This is a HTTP implementation of the MCP protocol
Project description
Simple HTTP MCP Server Implementation
This project provides a lightweight server implementation for the Model Context Protocol (MCP) over HTTP. It allows you to expose Python functions as tools and prompts that can be discovered and executed remotely via a JSON-RPC interface. It is intended to be used with a Starlette or FastAPI application (see demo).
The following badge corresponds to the example server for this project. Find it in the tests/app/ folder.
Features
- MCP Protocol Compliant: Implements the MCP specification for tool and prompts discovery and execution. No support for notifications.
- HTTP and STDIO Transport: Uses HTTP (POST requests) or STDIO for communication.
- Async Support: Built on
StarletteorFastAPIfor asynchronous request handling. - Type-Safe: Leverages
Pydanticfor robust data validation and serialization. - Stateful Context: Maintain state across tool calls using a context object.
- Request Access: Access the incoming request object from your tools.
Tools
Tools are the functions that can be called by the client.
Example:
- Define the arguments and output for the tools:
# app/tools/models.py
from pydantic import BaseModel, Field
class GreetInput(BaseModel):
question: str = Field(description="The question to answer")
class GreetOutput(BaseModel):
answer: str = Field(description="The answer to the question")
# Note: the description on Field will be passed when listing the tools.
# Having a description is optional, but it's recommended to provide one.
- Define the tools:
# app/tools/tools.py
from http_mcp.tools import ToolArguments
from app.tools.models import GreetInput, GreetOutput
def greet(args: ToolArguments[GreetInput, None]) -> GreetOutput:
return GreetOutput(answer=f"Hello, {args.inputs.question}!") # access inputs via args.inputs
# app/tools/__init__.py
from http_mcp.tools import Tool
from app.tools.models import GreetInput, GreetOutput
from app.tools.tools import greet
TOOLS = (
Tool(
func=greet,
input=GreetInput,
output=GreetOutput,
),
)
__all__ = ["TOOLS"]
- Instantiate the server:
# app/main.py
from starlette.applications import Starlette
from http_mcp.server import MCPServer
from app.tools import TOOLS
mcp_server = MCPServer(tools=TOOLS, name="test", version="1.0.0")
app = Starlette()
app.mount(
"/mcp",
mcp_server.app,
)
Stateful Context
This is the server context attribute; it can be seen as a global state for the server.
You can use a context object to maintain state across tool calls. The context object is passed to each tool call and can be used to store and retrieve data.
Example:
- Define a context class:
from dataclasses import dataclass, field
# app/context.py
@dataclass
class Context:
called_tools: list[str] = field(default_factory=list)
def get_called_tools(self) -> list[str]:
return self.called_tools
def add_called_tool(self, tool_name: str) -> None:
self.called_tools.append(tool_name)
- Instantiate the context and the server:
from app.tools import TOOLS
from app.context import Context
from http_mcp.server import MCPServer
mcp_server: MCPServer[Context] = MCPServer(
tools=TOOLS,
name="test",
version="1.0.0",
context=Context(called_tools=[]),
)
- Access the context in your tools:
from pydantic import BaseModel, Field
from http_mcp.tools import ToolArguments
from app.context import Context
class MyToolArguments(BaseModel):
question: str = Field(description="The question to answer")
class MyToolOutput(BaseModel):
answer: str = Field(description="The answer to the question")
async def my_tool(args: ToolArguments[MyToolArguments, Context]) -> MyToolOutput:
# Access the context
args.context.add_called_tool("my_tool")
...
return MyToolOutput(answer=f"Hello, {args.inputs.question}!")
Stateless Context
You can access the incoming request object from your tools. The request object is passed to each tool call and can be used to access headers, cookies, and other request data (e.g. request.state, request.scope).
from pydantic import BaseModel, Field
from http_mcp.tools import ToolArguments
class MyToolArguments(BaseModel):
question: str = Field(description="The question to answer")
class MyToolOutput(BaseModel):
answer: str = Field(description="The answer to the question")
async def my_tool(args: ToolArguments[MyToolArguments, None]) -> MyToolOutput:
# Access the request
auth_header = args.request.headers.get("Authorization")
...
return MyToolOutput(answer=f"Hello, {args.inputs.question}!")
Prompts
You can add interactive templates that are invoked by user choice.
- Define the arguments and output for the prompts:
from pydantic import BaseModel, Field
from http_mcp.mcp_types.content import TextContent
from http_mcp.mcp_types.prompts import PromptMessage
from http_mcp.prompts import Prompt
class GetAdvice(BaseModel):
topic: str = Field(description="The topic to get advice on")
include_actionable_steps: bool = Field(
description="Whether to include actionable steps in the advice", default=False
)
def get_advice(args: GetAdvice) -> tuple[PromptMessage, ...]:
"""Get advice on a topic."""
template = """
You are a helpful assistant that can give advice on {topic}.
"""
if args.include_actionable_steps:
template += """
The advice should include actionable steps.
"""
return (
PromptMessage(role="user", content=TextContent(text=template.format(topic=args.topic))),
)
PROMPTS = (
Prompt(
func=get_advice,
arguments_type=GetAdvice,
),
)
- Instantiate the server:
from starlette.applications import Starlette
from app.prompts import PROMPTS
from http_mcp.server import MCPServer
app = Starlette()
mcp_server = MCPServer(tools=(), prompts=PROMPTS, name="test", version="1.0.0")
app.mount(
"/mcp",
mcp_server.app,
)
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file http_mcp-0.2.0.tar.gz.
File metadata
- Download URL: http_mcp-0.2.0.tar.gz
- Upload date:
- Size: 473.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.6.11
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a51dfa8600c577f0176ed9351ea7e2c07aad6a63a8e53362746b35d6afa58418
|
|
| MD5 |
95722fe7642ec83db16d066a0ed2b387
|
|
| BLAKE2b-256 |
e4ac4535ca876427a41c5ad07df132d1b9a1b5b58de314da1f75e894a5d2cdd5
|
File details
Details for the file http_mcp-0.2.0-py3-none-any.whl.
File metadata
- Download URL: http_mcp-0.2.0-py3-none-any.whl
- Upload date:
- Size: 16.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.6.11
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
b7807b1b674caea63edfd173289ec9f8c5d88116786f2ead1e41261540f2cdce
|
|
| MD5 |
df68ba854b00af6205e4cd171703b24a
|
|
| BLAKE2b-256 |
4647f264efb4ec2e9c124f0f5f58eaf92c8fbfa2a8001ba51285412ac794e09b
|