Coadie MCP server reference.
Coadie’s MCP server lives at https://app.coadie.ca/mcp. It speaks JSON-RPC 2.0 over Streamable HTTP (POST, JSON responses, no event stream) and offers seven read-only tools and three building tools. Callers sign in either with a per-person bearer key or as Slackbot with Slack identity.
How do callers sign in?
| Question | How | Who it is for |
|---|---|---|
| Bearer key | Authorization: Bearer coadie_…. One key per person, made by Coadie, shown once, revocable. | Any MCP client |
| Slack identity | Slackbot’s MCP client with auth_type: slack_identity_auth. Requests are signed with Coadie’s Slack app secret (X-Slack-Signature, under five minutes old); the asker is params._meta.slack. Each Slack person links their own Coadie account once. | Slackbot |
Either way, a call runs as one Coadie person and sees exactly what that person could see. Building is allowed only on a connection marked for it.
Which tools does it offer?
| Question | Kind | What it returns |
|---|---|---|
ask_library | read-only | Numbered lines from the person’s library that answer a question, each with its file, slide and link; or a note that nothing answers |
list_shared_decks | read-only | Decks the person shared as a link, with sittings and people |
deck_readers | read-only | Who read one deck: people, sittings, completion, where people stop |
slide_attention | read-only | One deck slide by slide: seconds watched, share that reached it, returns |
list_shared_documents | read-only | Documents the person shared, with how many opened them |
document_readers | read-only | Who read one document, measured by depth |
reader_timeline | read-only | One reader’s visits in order, slide by slide |
start_build_deck | build | Reads a brief and asks back Coadie’s questions; returns a draft id |
answer_deck_questions | build | Answers or skips the questions and queues the build; returns a job id |
build_status | build | pending, building, done or failed, and the deck once done |
What are the limits?
- 60 calls a minute and 12 build steps an hour per connection by default. Past either, the answer is HTTP 429 with
Retry-After; nothing is lost. - Tools are built to answer within Slackbot’s 60-second limit: a deck is not built inside a call but queued, then checked with
build_status. - Protocol revisions spoken: 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26;
initializeechoes the client’s when supported. - Every call is logged by connection and tool, never with what was asked or answered.
Developer questions.
What is the Coadie MCP server address?
https://app.coadie.ca/mcp, over Streamable HTTP with JSON-RPC 2.0.
Does Coadie’s MCP server support Slackbot?
Yes, with Slack identity: requests signed by Coadie’s Slack app, and each Slack person linked to their own Coadie account.
Can an assistant change or delete decks through MCP?
No. Seven tools only read; three build a new deck, and only on a connection allowed to build.
See it on your own material.
Bring a handful of your decks. We’ll set up your workspace and build a first deck from them, with every line traced.