add R SDK/server

[simonpcouch]

Adds the mcptools R package to the Community Servers list. Admittedly, the placement is a bit strange here; mcptools is actually more like an SDK than a server, but I saw that yall have only listed SDKs developed in-house there:

servers/README.md

Lines 8 to 13 in 503202b

	- [C# MCP SDK](https://github.com/modelcontextprotocol/csharp-sdk)
	- [Go MCP SDK](https://github.com/modelcontextprotocol/go-sdk)
	- [Java MCP SDK](https://github.com/modelcontextprotocol/java-sdk)
	- [Kotlin MCP SDK](https://github.com/modelcontextprotocol/kotlin-sdk)
	- [Python MCP SDK](https://github.com/modelcontextprotocol/python-sdk)
	- [Typescript MCP SDK](https://github.com/modelcontextprotocol/typescript-sdk)

Description

Server Details

• Server:
• Changes to:

Motivation and Context

How Has This Been Tested?

Since the package implements both the client and server protocol, we test "round-trip" on every commit. We also test the client protocol against the GitHub MCP server in CI. Our tests of the server protocol against interactive only, using Claude Code and Claude Desktop.

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[olaservo]

I think this might make more sense in one of the other resources sections, maybe https://github.com/modelcontextprotocol/servers?tab=readme-ov-file#-frameworks ?

[simonpcouch]

Totally makes sense—thank you! Just made that happen.