Skip to content

docs: scope aligning imcp2 with MCP revision 2026-07-28 - #126

Draft
aterga wants to merge 1 commit into
mainfrom
claude/mcp-2026-07-28-alignment-doc
Draft

docs: scope aligning imcp2 with MCP revision 2026-07-28#126
aterga wants to merge 1 commit into
mainfrom
claude/mcp-2026-07-28-alignment-doc

Conversation

@aterga

@aterga aterga commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add a scoping/analysis document (docs/scoping-mcp-2026-07-28-alignment.md) that reads the MCP 2026-07-28 specification against the current imcp2 codebase and ranks the design improvements the revision enables. Analysis and sequencing only; no code changes.

The headline finding is that imcp2's deliberately stateless, plain-JSON, no-session design is exactly the shape the revision now mandates: 2026-07-28 removes protocol sessions, initialize, and Mcp-Session-Id, so most of the transport work ahead is deletion, gated on rmcp shipping a "modern" per-request path. The two immediate, imcp2-only wins are RFC 9207 iss and adopting Client ID Metadata Documents (CIMD) to replace open Dynamic Client Registration; CIMD also gives the scoping-client-branding.md work a DNS/TLS-authenticated, non-spoofable key.

The spec-strength labels (MUST / SHOULD / MAY) and repo citations were cross-checked by an adversarial verification pass; the doc records the corrections that pass applied.

Related issues

Follows up the MCP 2026-07-28 spec review. The first sequenced item, RFC 9207 iss, is implemented in a separate PR (branch claude/oauth-iss-rfc9207).

Changes

  • New file docs/scoping-mcp-2026-07-28-alignment.md, matching the repo's docs/scoping-*.md convention (status header, goal, ranked opportunities, sequencing).
  • Contents: what imcp2 already gets right (with the one not-yet-confirmed GET/DELETE→405 + session-id item flagged), a ranked list of thirteen opportunities (impact/effort/tractability + spec-strength labels + repo file:line citations), a deprecations table, a sequencing plan (iss first, CIMD next, then rmcp-gated items), and a corrections-applied section.

Testing

  • cargo build --locked --all-targets — n/a, docs-only change
  • cargo test --locked --all-targets — n/a, docs-only change
  • cargo fmt --all / cargo clippy --all-targets — n/a, docs-only change
  • npm test --prefix monitoring/mcp-status — n/a, dashboard unchanged

Checklist

  • I have read the Contributing guidelines.
  • Docs (README / comments) updated for any user-visible change.
  • No secrets, credentials, or internal-only information are included.

🤖 Generated with Claude Code

https://claude.ai/code/session_014T9N8USDfNK5yzznPGg7Ym


Generated by Claude Code

Add a scoping/analysis doc that reads the MCP 2026-07-28 specification
against the current imcp2 codebase and ranks the design improvements the
revision enables.

Headline finding: imcp2's deliberately stateless, plain-JSON, no-session
design is exactly the shape the revision now mandates (it removes protocol
sessions, `initialize`, and `Mcp-Session-Id`), so most transport work is
deletion gated on rmcp shipping a modern path. The two immediate,
imcp2-only wins are RFC 9207 `iss` (already shipped as its own PR) and
adopting Client ID Metadata Documents to replace open Dynamic Client
Registration, which also gives the client-branding work a non-spoofable
key.

The doc includes what imcp2 already gets right, a ranked list of thirteen
opportunities with impact/effort/tractability and spec-strength labels, a
deprecations table, a sequencing plan, and a record of the corrections the
verification pass applied. Analysis only; no code changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T9N8USDfNK5yzznPGg7Ym
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants