This implementation follows the official MCP specification, including proper message framing, transport layer implementation, and complete protocol lifecycle management. It provides a foundation for building federated MCP systems that can scale across multiple servers while maintaining security and standardization requirements.
This implementation follows the official MCP specification, including proper message framing, transport layer implementation, and complete protocol lifecycle management. It provides a foundation for building federated MCP systems that can scale across multiple servers while maintaining security and standardization requirements.
Add this configuration to your claude_desktop_config.json:
{
"mcpServers": {
"ruvnet-federated-mcp-github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-ruvnet-federated-mcp-github"
]
}
}
}Restart Claude Desktop, then ask:
"What tools do you have available from federated mcp?"
API Key Required
This server requires an API key from federated mcp. Add it to your environment or config.
| Variable | Required | Description |
|---|---|---|
| FEDERATED_MCP_API_KEY | Yes | Your federated mcp API key |
"What resources are available in federated mcp?"
Claude will query available resources and return a list of what you can access.
"Show me details about [specific item] in federated mcp"
Claude will fetch and display detailed information about the requested item.
"Create a new [item] in federated mcp with [details]"
Claude will use the appropriate tool to create the resource and confirm success.
We build custom MCP integrations for B2B companies. From simple connections to complex multi-tool setups.