my-mcp-server2
A Model Context Protocol server built with FastMCP that features dynamic tool loading and modular management via a dedicated tool directory. It supports both stdio and HTTP transport modes, enabling efficient development and deployment of custom MCP tools.
README
my-mcp-server2
my-mcp-server2 is a Model Context Protocol (MCP) server built with FastMCP featuring dynamic tool loading.
Features
- Dynamic Tool Loading: Tools are automatically discovered and loaded from
src/tools/ - One Tool Per File: Each tool is a single file with a function matching the filename
- FastMCP Integration: Leverages FastMCP for robust MCP protocol handling
- Configuration Management: Tool-specific configuration via
mcp.yaml - Fail-Fast: Server won't start if any tool fails to load
- Auto-Generated Tests: Automatic test generation for tool validation
Project Structure
src/
├── tools/ # Tool implementations (one file per tool)
│ ├── echo.py # Example echo tool
│ └── __init__.py # Auto-generated tool registry
├── core/ # Dynamic loading framework
│ ├── server.py # Dynamic MCP server
│ └── utils.py # Shared utilities
└── main.py # Entry point
mcp.yaml # Configuration file
tests/ # Generated tests
Quick Start
Option 1: Local Development (with Python/uv)
-
Install Dependencies:
uv sync -
Run the Server:
# Stdio mode (default MCP transport) uv run python src/main.py # HTTP mode with WebSocket MCP endpoint uv run python src/main.py --http # HTTP mode with custom host/port uv run python src/main.py --http --host 0.0.0.0 --port 8080 -
Using uv Scripts:
# Development mode (HTTP on port 3000) uv run dev # HTTP mode uv run dev-http # Stdio mode uv run start -
Add New Tools:
# Create a new tool (no tool types needed!) arctl mcp add-tool weather # The tool file will be created at src/tools/weather.py # Edit it to implement your tool logic
Option 2: Docker-Only Development (no local Python/uv required)
-
Build Docker Image:
arctl mcp build --verbose -
Run in Container:
docker run -i my-mcp-server2:latest -
Add New Tools:
# Create a new tool arctl mcp add-tool weather # Edit the tool file, then rebuild arctl mcp build
HTTP Transport Mode
The server supports running in HTTP mode for development and integration purposes.
Starting in HTTP Mode
# Command line flag
python src/main.py --http
# Environment variable
MCP_TRANSPORT_MODE=http python src/main.py
# Custom host and port
python src/main.py --http --host localhost --port 8080
Creating Tools
Basic Tool Structure
Each tool is a Python file in src/tools/ containing a function decorated with @mcp.tool():
# src/tools/weather.py
from core.server import mcp
from core.utils import get_tool_config, get_env_var
@mcp.tool()
def weather(location: str) -> str:
"""Get weather information for a location."""
# Get tool configuration
config = get_tool_config("weather")
api_key = get_env_var(config.get("api_key_env", "WEATHER_API_KEY"))
base_url = config.get("base_url", "https://api.openweathermap.org/data/2.5")
# TODO: Implement weather API call
return f"Weather for {location}: Sunny, 72°F"
Tool Examples
The generated tool template includes commented examples for common patterns:
# HTTP API calls
# async with httpx.AsyncClient() as client:
# response = await client.get(f"{base_url}/weather?q={location}&appid={api_key}")
# return response.json()
# Database operations
# async with asyncpg.connect(connection_string) as conn:
# result = await conn.fetchrow("SELECT * FROM weather WHERE location = $1", location)
# return dict(result)
# File processing
# with open(file_path, 'r') as f:
# content = f.read()
# return {"content": content, "size": len(content)}
Configuration
Configure tools in mcp.yaml:
tools:
weather:
api_key_env: "WEATHER_API_KEY"
base_url: "https://api.openweathermap.org/data/2.5"
timeout: 30
database:
connection_string_env: "DATABASE_URL"
max_connections: 10
Testing
Run the generated tests to verify your tools load correctly:
uv run pytest tests/
Development
Adding Dependencies
Update pyproject.toml and run:
uv sync
Code Quality
uv run black .
uv run ruff check .
uv run mypy .
Deployment
Docker
# Build image (handles lockfile automatically)
arctl mcp build
# Run container
docker run -i my-mcp-server2:latest
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.