MCP Boundary
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
MCP publication and MCP tool consumption both require authorization at the application execution boundary.
Publication exposes selected runtime capabilities through views, services or remote endpoints. The source distinguishes a modeled Action from the adapter that makes it callable and from the transport carrying the call. Published access does not remove authorization, transaction or lifecycle requirements.
Engineering rules
- Publish stable business capabilities instead of exposing arbitrary internal classes.
- Specify input/output, error, context and effect contracts per endpoint.
- Run the same business policy regardless of the chosen presentation or protocol.
- Verify actual protocol support in source, tests and versioned manifests.
Chapter outline (original LaTeX headings)
- Publication Starts with the Application Contract
- Compiling an Application for MCP
- Hosting the generated MCP surface
- Compiling an Application for OpenAPI
- Application and Package Publication
- The Two MCP Directions
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/publishing-applications-through-openapi-and-mcp.tex.