021-mcp-server
The MCP server: streamable HTTP, a small tool surface, OAuth discovery that bootstraps itself
Lifecycle approvedImplementation pendingVerification unknownQualification unknown
One remote MCP server over streamable HTTP, stateless per request, serving every client that speaks the protocol. Seven tools, no more: capture, search, fetch, list, update, forget, and relate. Authorization is the chassis's resource server, so an unauthenticated initialize answers the challenge that lets a client discover the authorization server and register itself without the user pasting anything. Tool results carry envelopes and the framing statement, and the tool descriptions themselves never contain recalled content.
Read the full pinned specification ↗Relationships
depends on
depended on by
Claimed units
- establishes
{ "kind": "file", "path": "crates/aicortex-mcp/Cargo.toml" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/lib.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/transport.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/session.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/tools.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/resources.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/compat.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/src/render.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/tests/protocol.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/tests/tools.rs" } - establishes
{ "kind": "file", "path": "crates/aicortex-mcp/testdata/sessions/" } - extends
{ "nature": "additive", "spec": "010-chassis-adoption-and-workspace", "unit": { "kind": "file", "path": "apps/aicortex/src/cell.rs" } } - extends
{ "nature": "additive", "spec": "020-http-api-and-scopes", "unit": { "kind": "file", "path": "crates/aicortex-api/src/dto.rs" } }
Source headings
- 021: The MCP server
- 1. Purpose
- 2. Territory
- 3. Behavior
- 4. Functional requirements
- 5. Acceptance criteria
- 6. Out of scope
- 7. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.