MCP-00: MCP server implementation tracker

[Chris0Jeky]

Overview

Implementation tracker for the Taskdeck MCP server exposing board resources and tools to external AI agents (Claude Code, Cursor, etc.).

Spike: #619 (completed) — architecture document at docs/spikes/SPIKE_619_COMPLETED.md

Key Decisions (from spike)

• Official MCP C# SDK (ModelContextProtocol v1.2.0, co-maintained by Microsoft)
• Embedded in API process — --mcp flag for stdio mode; HTTP alongside REST on same Kestrel instance
• stdio first, Streamable HTTP added in Phase 3 for cloud/remote
• 9 resources under taskdeck:// URI scheme
• 9 tools: 2 read + 5 write + 2 proposal management; approve_proposal intentionally excluded (GP-06)
• Auth: OS process identity (stdio), API keys with tdsk_ prefix (HTTP)
• Write tools return proposal IDs — users approve in web UI, agents poll via get_proposal_status

Implementation Phases

• Phase 1: Minimal prototype — one resource + stdio (MCP-01: Phase 1 — Minimal MCP prototype (one resource, stdio, Claude Code) #652)
• Phase 2: Full resource + tool inventory (MCP-02: Phase 2 — Full MCP resource and tool inventory #653)
• Phase 3: HTTP transport + auth (MCP-03: Phase 3 — HTTP transport and API key authentication #654)
• Phase 4: Production hardening (deferred to v0.4.0+ demand) (MCP-04: Phase 4 — MCP production hardening (deferred to v0.4.0+) #655)

Dependencies

• Reuses same Application layer services as LLM tool-calling (LLM-05: LLM tool-calling implementation tracker #647)
• Builds on existing ITaskdeckToolRegistry and AgentPolicyEvaluator (AGT-02: Add tool registry, policy evaluator, and bounded inbox-triage template #337)
• Phase 2 tool inventory mirrors LLM-06: Phase 1 — Read tools, orchestrator, and provider tool-calling extension #649 tool abstractions

References

• docs/spikes/SPIKE_619_COMPLETED.md — full architecture document
• docs/decisions/ADR-0017-agent-tool-registry-review-first.md — tool registry design
• docs/GOLDEN_PRINCIPLES.md GP-06 — review-first automation safety