@appport/mcp

Expose AppPort capabilities as MCP tools.

import { createMcpBridge } from "@appport/mcp";

const bridge = createMcpBridge(application, { session });

bridge.listTools();
await bridge.callTool("documents_save", { documentId, content });

The layering matters:

AI -> MCP -> AppPort -> application

AppPort does not compete with MCP; it is the application protocol underneath it. A capability that is already defined, validated, versioned and authorized becomes an agent tool without a second definition, and the agent's session decides what it may call. A tool call runs the same dispatch pipeline as any other request, so INVALID_INPUT and FORBIDDEN reach the agent as tool errors rather than as unexpected behaviour.

Tool names map to capability names (documents.save becomes documents_save) and the tool's input schema is the capability's published JSON Schema. Stream capabilities and the reserved appport.* namespace are excluded by default.