Connect an AI client (MCP)

These docs are also a machine-readable server. If your team builds with an AI coding agent — Cursor, VS Code, Claude Code, or anything that speaks the Model Context Protocol — point it here and it can search and read this entire guide, the API reference included, while you integrate.

The docs MCP server

Streamable-HTTP endpoint, no credentials needed:

https://docs.rostergiving.com/mcp

Add to Cursor  ·  Add to VS Code

Claude Code

claude mcp add --transport http roster-docs https://docs.rostergiving.com/mcp

Claude (claude.ai / Desktop) — Settings → Connectors → Add custom connector, name it roster-docs and paste the URL above. No auth fields needed.

Anything else — it is a standard MCP server over streamable HTTP; add it the way your client adds remote servers.

The API MCP server — execute real sandbox calls

This one acts: it imports churches, opens donor sessions, reads the event feed and fires the sandbox simulators — authenticated with your own sk_test key, sent per-request as a Bearer token. The MCP proxy (operated by Scalar) forwards the Authorization header in passthrough mode and does not store it; the Roster API receives your key exactly as a direct HTTP call would — and, as always, keeps only a hash:

https://mcp.scalar.com/mcp/5a28ecf9-4b81-4099-b09b-dc85490152b2

Claude Code

claude mcp add --transport http roster-api \
  https://mcp.scalar.com/mcp/5a28ecf9-4b81-4099-b09b-dc85490152b2 \
  --header "Authorization: Bearer $ROSTER_KEY"

Add to Cursor  ·  Add to VS Code  — then add an Authorization: Bearer sk_test_… header to the server's config.

Calls without a key (or with a revoked one) get the API's normal opaque 401 — the MCP server adds no credentials of its own. Note for claude.ai custom connectors: they can't attach a static header yet, so use the docs server there and the API server in Claude Code / Cursor / VS Code.

Your sk_test key comes from the Developers section of your partner workspace (your workspace owner can issue and rotate it). Keys are shown once and stored hashed — see Introduction for the conventions.