Roster MCP Server · Phase 1 · Internal

Project Documents

The spec set for connecting Roster to claude.ai and Claude Cowork via a remote MCP server. Start with the PRD; the two technical writeups split the build into its two workstreams.

PRD — Claude Connector (Phase 1)Start here

Problem, solution, success metrics, scope, 11-tool catalog, requirements, decisions D-1–D-9, rollout plan, and test cases.

MCP Server & OAuth — Implementation Writeup

Architecture and topology, MCP server behavior (transport, envelope, errors, timezone), Roster token model and credential bridge, the Cloudflare Workers build plan (verified against vendor docs 2026-06-10), revocation, environments, and the .NET alternative.

Tool Catalog — Technical Deep Dive & Specs

All 11 tools: verified upstream mappings (portal page → internal API → stored procedure), MCP tool definitions with input schemas and response shapes, the E1–E9 new-endpoint workstream, and PRD divergence decisions.

Connect Roster to ClaudeCustomer-facing

Draft help article for docs.getroster.com: requirements, one-minute setup, five starter prompts, what Claude can and cannot access, switching brands, disconnecting, FAQ.

Source: roster-brain · projects/roster-mcp-server · deployed via prototypes.roster.website