io.github.jamesmontemagno/monkeymcp MCP Server
io.github.jamesmontemagno/monkeymcp
MCP server providing monkey data, journeys, and location services for various monkey species.
What is the io.github.jamesmontemagno/monkeymcp MCP server?
The Monkey MCP server is a Model Context Protocol implementation built with .NET 9.0 that provides tools for accessing monkey data, generating simulated journeys, and retrieving location-based activities for different monkey species. It exposes tools to query monkey information, create unique journey paths with activities and health statistics, and supports both stdio and HTTP (SSE) transport methods.
This server enables AI agents to interact with a monkey data service that includes information about various monkey species, their behaviors, and simulated journeys. You can retrieve monkey details, generate species-specific journey paths with activities like foraging and grooming, and access health statistics and movement patterns. It's useful for applications requiring monkey species data, behavioral simulation, or location-based activity generation.
How to install io.github.jamesmontemagno/monkeymcp
Copy-paste configuration for popular MCP clients.
Tools & capabilities
Tools this server exposes to the agent.
GetMonkeys— Returns a JSON serialized list of all available monkeysGetMonkey— Retrieves information about a specific monkey by nameGetMonkeyJourney— Creates a unique journey path with activities and health stats for a specific monkeyGetAllMonkeyJourneys— Generates journey paths for all available monkeys
Use cases
- Retrieve detailed information about specific monkey species and their characteristics
- Generate simulated journeys showing monkey movement paths, activities, and health metrics
- Create species-specific behavioral simulations (e.g., hot spring bathing for macaques, swimming for proboscis monkeys)
- Access monkey location data and activity logs with energy/happiness tracking
- Build educational or entertainment applications featuring monkey behavior and ecology
io.github.jamesmontemagno/monkeymcp MCP server FAQ
It provides tools to query monkey species data, generate simulated journeys with species-specific activities and health statistics, and retrieve location-based information for various monkey types including baboons, howler monkeys, Japanese macaques, proboscis monkeys, and golden snub-nosed monkeys.
Yes, the server is available under the MIT License and can be deployed locally via Docker or as a remote HTTP service.
You can install it via one-click buttons in the README for VS Code/VS Insiders, or manually configure it in your MCP client settings using either the remote Azure Functions endpoint (HTTP) or Docker container method.
The server supports both stdio transport (for local execution) and HTTP Server-Sent Events (SSE) transport (for web-based clients), running on http://localhost:3001 by default for the SSE version.
No authentication is required. The remote Azure Functions endpoint and Docker container are publicly accessible.
The server includes data and simulations for baboons, howler monkeys, Japanese macaques, proboscis monkeys, and golden snub-nosed monkeys, each with species-specific behaviors and activities.
README (reference)
Source of truth, from the repository.
Monkey - Model Context Protocol (MCP) Server
Overview
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.
Try it
Quick Install for VS Code & VS
Configure in VS Code with GitHub Copilot, Claude Desktop, or other MCP clients:
Option 1: Remote Azure Functions Server (Recommended)
{
"servers": {
"monkeymcp": {
"url": "https://func-monkeymcp-3t4eixuap5dfm.azurewebsites.net/",
"type": "http"
}
},
"inputs": []
}
Option 2: Docker Container
{
"inputs": [],
"servers": {
"monkeymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"jamesmontemagno/monkeymcp"
],
"env": {}
}
}
}
Features
Core Components
- MCP Server: Built using the ModelContextProtocol library (version 0.1.0-preview.2)
- Standard I/O Transport: Uses stdio for communication with clients
- Custom Tool Integration: Includes examples of how to create and register MCP tools
Services
-
MonkeyService: A sample service that fetches monkey data from an API endpoint
- Provides methods to retrieve a list of all monkeys or find a specific monkey by name
- Caches results for better performance
-
MonkeyLocationService: A service that generates unique journeys and activities for monkeys
- Creates randomized path points based on monkey species behavior
- Generates species-specific activities (grooming, howling, hot spring bathing, etc.)
- Provides health statistics and movement patterns
- Each journey includes fun activities like eating bananas, cleaning other monkeys, and exploration
Available Tools
The server exposes several tools that can be invoked by clients:
Monkey Tools
- GetMonkeys: Returns a JSON serialized list of all available monkeys
- GetMonkey: Retrieves information about a specific monkey by name
- GetMonkeyJourney: Creates a unique journey path with activities and health stats for a specific monkey
- GetAllMonkeyJourneys: Generates journey paths for all available monkeys
Configuration Options
Hosting Configuration
The server uses Microsoft.Extensions.Hosting (version 9.0.3) which provides:
- Configuration from multiple sources (JSON, environment variables, command line)
- Dependency injection for services
- Logging capabilities
Logging Options
Several logging providers are available:
- Console: Logs to standard output
- Debug: Logs for debugging purposes
- EventLog: Logs to the system event log (when running on Windows)
- EventSource: Provides ETW (Event Tracing for Windows) integration
Getting Started
Prerequisites
- .NET 9.0 SDK or later
- Basic understanding of the Model Context Protocol (MCP)
Running the Server
- Clone this repository
- Navigate to the project directory
- Build the project:
dotnet build - Configure with VS Code or other client:
"monkeyserver": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"/Users/jamesmontemagno/GitHub/TestMCP/MonkeyMCP/MonkeyMCP.csproj"
]
}
Update the path to the project
Extending the Server
To add custom tools:
- Create a class and mark it with the
[McpServerToolType]attribute - Add methods with the
[McpServerTool]attribute - Optionally add
[Description]attributes to provide documentation
Example:
[McpServerToolType]
public static class CustomTool
{
[McpServerTool, Description("Description of what the tool does")]
public static string ToolMethod(string param) => $"Result: {param}";
}
Server-Sent Events Implementation (MonkeyMCPSSE)
Overview
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
Features
- HTTP-based Transport: Runs on
http://localhost:3001by default - Server-Sent Events: Enables real-time, one-way communication from server to client
- ASP.NET Core Integration: Built using ASP.NET Core's web server capabilities
- MCP over HTTP: Implements the Model Context Protocol over HTTP transport
Running the SSE Server
- Navigate to the MonkeyMCPSSE directory
- Build and run the project:
- Connect and run in VS Code or using MCP Inspector
npx @modelcontextprotocol/inspector
Implementation Details
The 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.
Project Structure
- /MonkeyMCP: Main project directory
- MonkeyService.cs: Implementation of the service to fetch monkey data
- MonkeyTools.cs: MCP tools for accessing monkey data
- Program.cs: Entry point that configures and starts the MCP server
Dependencies
- Microsoft.Extensions.Hosting (9.0.3): Provides hosting infrastructure
- ModelContextProtocol (0.1.0-preview.2): MCP server implementation
- System.Text.Json (9.0.3): JSON serialization/deserialization
License
This project is available under the MIT License.
<!-- mcp-name: io.github.jamesmontemagno/monkeymcp -->MonkeyLocationService Features
The MonkeyLocationService provides rich simulation capabilities:
Monkey Type Configurations
- Baboons: Savanna dwellers with social grooming behaviors and root foraging
- Howler Monkeys: Forest inhabitants known for territorial howling and leaf eating
- Japanese Macaques: Mountain monkeys that enjoy hot springs and snow play
- Proboscis Monkeys: Mangrove specialists that swim and show off their distinctive noses
- Golden Snub-Nosed Monkeys: High-altitude acrobats that huddle for warmth
Journey Components
- Path Points: GPS coordinates showing where the monkey traveled
- Activities: Species-specific behaviors with energy costs/benefits
- Health Stats: Energy, happiness, hunger, social, stress, and health metrics
- Time Tracking: Start/end times and activity durations
- Distance Calculation: Total journey distance using Haversine formula
Unique Activities Include
- Banana finding and eating
- Mutual grooming sessions
- Territory marking
- Hot spring bathing (macaques)
- Swimming (proboscis monkeys)
- Acrobatic displays
- Social interactions
- Foraging and exploration
Related MCP servers

Oh My Posh Configurator
Design beautiful terminal prompts visually without editing JSON—drag, drop, customize, and export Oh My Posh configurations.

Wiggle
A coordination layer for autonomous agents: rooms, messaging, inbox, roles, and polls.
Make money with x402. See what's earning, find profitable gaps, and price your service right.
View repository →Find where the money is in AI services. See what's earning and find market gaps.
View repository →
io.github.jamhimself/robinx-mcp
Robinhood Chain (4663) caller accuracy + token intel, graded vs real price since genesis. x402-paid

Keelen
Autonomous dev team steered from chat: plain-English requests in, tested merged PRs out.
