@ttoss/http-server-mcp
Model Context Protocol (MCP) server integration for @ttoss/http-server.
Installation
pnpm add @ttoss/http-server-mcp
Quick Start
import { App, bodyParser, cors } from '@ttoss/http-server';
import { createMcpRouter, McpServer, z } from '@ttoss/http-server-mcp';
// Create MCP server
const mcpServer = new McpServer({
name: 'my-mcp-server',
version: '1.0.0',
});
// Register tools
mcpServer.registerTool(
'get-weather',
{
description: 'Get weather information for a location',
inputSchema: {
location: z.string().describe('City name'),
},
},
async ({ location }) => ({
content: [
{
type: 'text',
text: `Weather in ${location}: Sunny, 72°F`,
},
],
})
);
// Create HTTP server
const app = new App();
app.use(cors());
app.use(bodyParser());
// Mount MCP router
const mcpRouter = createMcpRouter(mcpServer);
app.use(mcpRouter.routes());
app.listen(3000, () => {
console.log('MCP server running on http://localhost:3000/mcp');
});
apiCall — Generic HTTP Helper
apiCall is a generic HTTP helper for use inside MCP tool handlers. It works with any URL — your own REST API, third-party APIs, public APIs, or services using x-api-key or any other header scheme.
Use getApiHeaders in createMcpRouter to configure which headers from the incoming MCP request are automatically forwarded to every apiCall. Tool handlers stay clean and auth-agnostic.
Bearer token forwarding
import { apiCall, createMcpRouter, McpServer } from '@ttoss/http-server-mcp';
const mcpServer = new McpServer({ name: 'my-server', version: '1.0.0' });
mcpServer.registerTool(
'list-portfolios',
{ description: 'List all portfolios', inputSchema: {} },
async () => {
// Bearer token is forwarded automatically — no manual wiring
const data = await apiCall('GET', '/portfolios');
return { content: [{ type: 'text', text: JSON.stringify(data) }] };
}
);
const mcpRouter = createMcpRouter(mcpServer, {
apiBaseUrl: `http://localhost:${process.env.PORT}/api/v1`,
// Extract the caller's Bearer token and inject it into every apiCall
getApiHeaders: (ctx) => ({ Authorization: ctx.headers.authorization ?? '' }),
});
x-api-key forwarding
const mcpRouter = createMcpRouter(mcpServer, {
apiBaseUrl: 'https://internal-service/api',
getApiHeaders: (ctx) => ({
'x-api-key': ctx.headers['x-api-key'] as string,
}),
});
Third-party or public APIs (full URL, no context required)
mcpServer.registerTool(
'get-rates',
{ description: 'Currency rates', inputSchema: {} },
async () => {
// Full URL — works entirely outside any context
const rates = await apiCall('GET', 'https://api.exchangerate.host/latest');
return { content: [{ type: 'text', text: JSON.stringify(rates) }] };
}
);
POST with a body
const result = await apiCall('POST', '/portfolios', {
body: { name: 'Growth Fund' },
});
Per-call header override
// Context-injected headers are merged; per-call headers take precedence
const data = await apiCall('GET', 'https://partner.api.com/data', {
headers: { Authorization: 'Bearer fixed-service-token' },
});
apiCall throws with a clear message when called with a relative path and no apiBaseUrl is configured in the context.
API Reference
createMcpRouter(server, options?)
Creates a Koa router configured to handle MCP protocol requests.
Parameters:
server(McpServer) - MCP server instance with registered tools and resourcesoptions(McpRouterOptions) - Optional configurationpath(string) - HTTP path for MCP endpoint (default:'/mcp')sessionIdGenerator(() => string) - Session ID generator for stateful servers (default:undefinedfor stateless)apiBaseUrl(string) - Base URL prepended to relative paths inapiCallgetApiHeaders((ctx: Context) => Record<string, string>) - Return headers to inject into everyapiCallfor this request (auth tokens, API keys, trace headers, etc.)
Returns: Router - Koa router instance
apiCall(method, url, options?)
Generic HTTP helper for use inside MCP tool handlers.
Parameters:
method(string) - HTTP method ('GET','POST','PUT','DELETE', …)url(string) - Full URL or a path starting with/(prepended withapiBaseUrl)options.body(unknown, optional) - Request body, serialised as JSONoptions.headers(Record<string, string>, optional) - Per-call header overrides; merged on top of context-injected headers
Returns: Promise<unknown> - Parsed JSON response body
Examples
Basic Tool
import { McpServer, z } from '@ttoss/http-server-mcp';
const server = new McpServer({
name: 'calculator',
version: '1.0.0',
});
server.registerTool(
'add',
{
description: 'Add two numbers',
inputSchema: {
a: z.number().describe('First number'),
b: z.number().describe('Second number'),
},
},
async ({ a, b }) => ({
content: [
{
type: 'text',
text: `${a} + ${b} = ${a + b}`,
},
],
})
);
Multiple Tools
server.registerTool(
'multiply',
{
description: 'Multiply two numbers',
inputSchema: {
a: z.number(),
b: z.number(),
},
},
async ({ a, b }) => ({
content: [{ type: 'text', text: String(a * b) }],
})
);
server.registerTool(
'divide',
{
description: 'Divide two numbers',
inputSchema: {
a: z.number(),
b: z.number(),
},
},
async ({ a, b }) => {
if (b === 0) {
throw new Error('Division by zero');
}
return {
content: [{ type: 'text', text: String(a / b) }],
};
}
);
Custom Path
const router = createMcpRouter(server, {
path: '/api/mcp',
});
Resources
server.resource(
'config://app',
'Application configuration',
'application/json',
async () => ({
contents: [
{
uri: 'config://app',
mimeType: 'application/json',
text: JSON.stringify({ version: '1.0.0', env: 'production' }),
},
],
})
);
With CORS and Multiple Endpoints
import { App, bodyParser, cors, Router } from '@ttoss/http-server';
import { createMcpRouter } from '@ttoss/http-server-mcp';
const app = new App();
app.use(cors());
app.use(bodyParser());
// Health check endpoint
const healthRouter = new Router();
healthRouter.get('/health', (ctx) => {
ctx.body = { status: 'ok' };
});
// MCP endpoint
const mcpRouter = createMcpRouter(mcpServer);
app.use(healthRouter.routes());
app.use(mcpRouter.routes());
app.listen(3000);
Protocol Details
This package implements the Model Context Protocol over HTTP using JSON responses (no SSE streaming). It uses the StreamableHTTPServerTransport from the MCP SDK with enableJsonResponse: true and adapts Koa's context-based middleware to work with the MCP SDK's Node.js request/response expectations.
Supported HTTP methods:
POST /mcp- Send JSON-RPC requests/notificationsDELETE /mcp- Terminate session (optional)
Client requirements (per MCP spec):
Content-Type: application/jsonAccept: application/json, text/event-stream
Stateless vs stateful mode:
- Stateless (default,
sessionIdGenerator: undefined) — a fresh transport is created per HTTP request. No session tracking. Suitable for serverless environments and simple integrations. - Stateful (
sessionIdGeneratorprovided) — a single shared transport handles all requests and tracks sessions by ID.
Related Packages
- @ttoss/http-server - HTTP server foundation
- @modelcontextprotocol/sdk - MCP SDK