On this page
Expose capabilities through MCP
Separate developer documentation from authorized application operations.
Keep developer documentation and application operations on separate servers. They have different identities, trust boundaries and data-access policies.
Developer documentation server
Fabricators.DeveloperMcp is a readonly stdio .NET tool. It exposes a reviewed, embedded documentation catalog. It cannot inspect arbitrary local files, resolve runtime secrets or act on ERP customer data. The existing embedded catalog has not yet been replaced by the new full documentation bundle.
Application server
Fabricators.Mcp uses the official MCP SDK. Typed contributions declare their capability descriptors and execution contracts. Progressive discovery and dispatch keep a small external tool surface: discover the relevant capabilities, then call one with explicit typed arguments. Bound discovery results; do not dump every app schema into the client's context on startup.
The product must supply caller binding and tool authorization. Recheck rights at dispatch time, including app activation, licenses, tenant/company scope, quotas, required assurance and approvals. Discovery is not an authorization grant.
Transport
Fabricators.Mcp.AspNetCore maps authenticated stateless Streamable HTTP. Configure the host's authentication and policy before mapping it. A connector is not a trusted native app simply because it can obtain an OAuth token.
Contribution contract
Our own apps and third-party apps follow the same contribution rules. Keep tool IDs stable and namespaced by publisher/app, validate bounded input, return safe errors, and audit consequential work at the owning transaction boundary.
Next: MCP ports, dispatcher API and strong-authentication requirements.