README
¶
mcp-server-core
The platform-agnostic core shared by Deployment Theory's desktop MCP servers (windows-mcp-server and macos-mcp-server).
Everything a desktop-automation MCP server needs that is not about one operating system lives here, so the two servers cannot drift apart on the protocol, the toolset engine, the guardrail wiring or the journey runner:
| Package | What it holds |
|---|---|
inventory |
The toolset filter/registration engine (modelled on github-mcp-server): toolsets, personas as presets, --tools/--exclude-tools, fixed resources, prompts. |
toolkit |
Tool-handler building blocks: argument coercion (ArgsMap, Optional*), result constructors, the assertion algebra, protected-path guards, the evidence sink, the planner contract, and generic dependency injection (MustDepsFromContext[D]). |
surface |
One constructor for the MCP server every entry point shares (stdio, offline capture, conformance host), the single-call receiving-middleware chain, SEP-2549 cache hints, pinned capabilities, completion, the wire recorder. |
runtime |
Guardrail orchestration over agentweave-harness: policy loading, the signal registry, the receiving chain, egress provisioning (enforcer injected), the harness servant (dialer injected), the planner, the journey runner, evidence sealing and export, and the operator-facing policy operations. |
journeys, runrecord |
Journeys-as-code: the document vocabulary, compilation to a plan, and the OTLP/JSON run record. |
mcpspec, mcpconf |
The vendored MCP schema loader (offline wire validation) and the official conformance-suite results reader. |
conformance (-tags conformance) |
The suite's named fixtures and the generic loopback Streamable-HTTP host. Never part of a normal build. |
Rules
- No platform build tags. CI refuses them. A server supplies its platform
through the agentweave-harness interfaces (
signals.SystemProbe,signals.HealthProbe,contain.SystemActuator,egress.Enforcer) and its own dependency type. - Secrets come from the environment, named by
runtime.EnvNames{Prefix}so each server keeps its own prefix (WINDOWS_MCP_,MACOS_MCP_). - Pin tags, never
replace. The servers import this module by tag; CI refuses areplacedirective.
Protocol
Targets MCP revision 2026-07-28 on modelcontextprotocol/go-sdk. The
revisions this module vendors for offline validation are listed in
schema/versions.json.
License
MIT — see LICENSE.
Directories
¶
| Path | Synopsis |
|---|---|
|
Package conformance holds what the official MCP conformance suite (github.com/modelcontextprotocol/conformance) needs from a server under test and nothing a released binary should carry: the suite's named fixture tools, resources and prompts, a loopback-only Streamable HTTP host, and a recovering middleware so one broken handler cannot cost the evidence for every scenario after it.
|
Package conformance holds what the official MCP conformance suite (github.com/modelcontextprotocol/conformance) needs from a server under test and nothing a released binary should carry: the suite's named fixture tools, resources and prompts, a loopback-only Streamable HTTP host, and a recovering middleware so one broken handler cannot cost the evidence for every scenario after it. |
|
Package inventory is a transport-agnostic, domain-agnostic registry for MCP tools, resources, and prompts.
|
Package inventory is a transport-agnostic, domain-agnostic registry for MCP tools, resources, and prompts. |
|
Package journeys is the declarative model of a user journey: a named sequence of UI actions, each with assertions about the resulting screen and evidence to capture.
|
Package journeys is the declarative model of a user journey: a named sequence of UI actions, each with assertions about the resulting screen and evidence to capture. |
|
Package mcpconf reads the results of the official Model Context Protocol conformance suite (github.com/modelcontextprotocol/conformance) and renders them as the project's committed compliance report.
|
Package mcpconf reads the results of the official Model Context Protocol conformance suite (github.com/modelcontextprotocol/conformance) and renders them as the project's committed compliance report. |
|
Package mcpspec loads the vendored Model Context Protocol JSON Schemas and validates wire JSON against them.
|
Package mcpspec loads the vendored Model Context Protocol JSON Schemas and validates wire JSON against them. |
|
Package runrecord builds the OpenTelemetry trace that records a journey run, and serialises it as OTLP/JSON.
|
Package runrecord builds the OpenTelemetry trace that records a journey run, and serialises it as OTLP/JSON. |
|
Package runtime is the shared orchestration layer of an MCP server built on mcp-server-core: policy loading, the guardrail registry, the receiving middleware chain, egress provisioning, the harness servant, the planner, the journey runner, evidence sealing and the operator-facing policy operations.
|
Package runtime is the shared orchestration layer of an MCP server built on mcp-server-core: policy loading, the guardrail registry, the receiving middleware chain, egress provisioning, the harness servant, the planner, the journey runner, evidence sealing and the operator-facing policy operations. |
|
Package surface builds the protocol-facing MCP server every entry point of a server shares: the stdio server operators run, the in-process capture used for the offline pre-flight, and the loopback HTTP host the official conformance suite connects to.
|
Package surface builds the protocol-facing MCP server every entry point of a server shares: the stdio server operators run, the in-process capture used for the offline pre-flight, and the loopback HTTP host the official conformance suite connects to. |
|
Package toolkit holds the platform-agnostic building blocks an MCP server built on mcp-server-core shares: argument coercion, result constructors, the assertion algebra, protected-path guards, the evidence sink, the planner contract and the dependency-injection plumbing that puts a server's dependencies on the request context.
|
Package toolkit holds the platform-agnostic building blocks an MCP server built on mcp-server-core shares: argument coercion, result constructors, the assertion algebra, protected-path guards, the evidence sink, the planner contract and the dependency-injection plumbing that puts a server's dependencies on the request context. |
Click to show internal directories.
Click to hide internal directories.