Skip to main content
The Deck docs are available as a hosted MCP server:
Connect it to any MCP client and your AI tool can search this site and read full pages while it works, instead of relying on training data or web search. The server is read-only and covers documentation only. It has no access to your Deck account or your data, and it cannot call the Deck API.

Connect it

You can also connect from any docs page: open the context menu at the top of the page to copy the server URL or add it to Cursor or VS Code in one click.

What it provides

The server also exposes the Deck skill as an MCP resource, so connected agents can load Deck integration guidance without installing skill.md separately. Once connected, your tool decides when to search. Ask it things like “How does session reuse work in Deck?” or “Write a webhook handler for task_run.completed” and it pulls the answer from the current docs.

Limitations

  • Docs only. The server can’t see your runs, credentials, or metrics. For account questions in chat form, use Deck in Slack. For programmatic access, use the API.
  • Read-only. Apart from submit_feedback, the server only searches and reads documentation.
For other ways to give AI tools Deck context, including the Deck skill, a context prompt, and LLM-formatted doc exports, see Build with AI.