MCP server providing monkey data, journeys, and location services for various monkey species.
This is a Model Context Protocol (MCP) server implementation built with .NET 9.0. The MCP server provides a communication protocol for facilitating interactions between various components in a model-driven system. This implementation demonstrates how to set up a basic MCP server with custom tools and services.
Configure in VS Code with GitHub Copilot, Claude Desktop, or other MCP clients:
{
"servers": {
"monkeymcp": {
"url": "https://func-monkeymcp-3t4eixuap5dfm.azurewebsites.net/",
"type": "http"
}
},
"inputs": []
}
{
"inputs": [],
"servers": {
"monkeymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"jamesmontemagno/monkeymcp"
],
"env": {}
}
}
}
MonkeyService: A sample service that fetches monkey data from an API endpoint
MonkeyLocationService: A service that generates unique journeys and activities for monkeys
The server exposes several tools that can be invoked by clients:
The server uses Microsoft.Extensions.Hosting (version 9.0.3) which provides:
Several logging providers are available:
dotnet build"monkeyserver": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"/Users/jamesmontemagno/GitHub/TestMCP/MonkeyMCP/MonkeyMCP.csproj"
]
}
Update the path to the project
To add custom tools:
[McpServerToolType] attribute[McpServerTool] attribute[Description] attributes to provide documentationExample:
[McpServerToolType]
public static class CustomTool
{
[McpServerTool, Description("Description of what the tool does")]
public static string ToolMethod(string param) => $"Result: {param}";
}
The MonkeyMCPSSE project provides an alternative implementation of the Monkey MCP server using Server-Sent Events (SSE) over HTTP instead of stdio transport. This implementation runs as a web server, making it ideal for web-based clients and scenarios requiring HTTP-based communication.
Read more about SSE best practices for security here
http://localhost:3001 by defaultnpx @modelcontextprotocol/inspectorThe SSE implementation uses ASP.NET Core's built-in web server capabilities while maintaining the same monkey data service and tools as the stdio version. This makes it easy to switch between transport methods while keeping the core functionality intact.
This project is available under the MIT License.
The MonkeyLocationService provides rich simulation capabilities:
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
docker run -i --rm docker.io/jamesmontemagno/monkeymcp:2.0.3Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-jamesmontemagno-monkeymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/jamesmontemagno/monkeymcp:2.0.3"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedocker.io/jamesmontemagno/monkeymcp:2.0.3dockerio.github.jamesmontemagno/monkeymcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.