Define Mcp Agent Entrypoint Surface
Artifacts
Official change artifacts tracked under openspec/.
The current hosted MCP surface exposes every read and event-subscription tool in one flat tools/list response. The first footprint tranche removes duplicated prose, but it intentionally preserves the 14-tool topology. That is still too broad for the normal read/query setup path.
design-notes/mcp-tool-surface-token-footprint-2026-06-08.md measured the live hosted MCP tools/list response at about 49.6 KB for 14 tools. The prose cleanup tranche reduced the complete surface to about 38.5 KB, but kept a flat tool topology. That is useful hygiene, not the SLVP ideal.
Affected capabilities
Capability specs this change proposes to modify.
The MCP adapter's recommended setup path SHALL expose one profile-free normal read entrypoint. The operator SHALL NOT choose or understand core, events, full, toolsets, or equivalent mechanism labels before connecting an agent.
The reference operator dashboard SHALL expose one ordinary-agent setup page for grant-scoped AI-app access. The page SHALL be reachable from dashboard navigation and deployment readiness, and SHALL remain separate from owner-token issuance.
Project notes
Change-local notes that support this workstream but have not been promoted into the official change artifacts.
Define Mcp Agent Entrypoint Surface
1 notes · 1 research note · updated