October 27, 2026
Connect Scindo to Claude
Claude forgets what your team decided. Scindo doesn't. Here is how to let Claude read it, and write to it, without pasting a key.
You ask Claude to help with a change. It writes good code against a decision your team reversed last week, because it never saw the thread. You paste the thread. Next week you paste it again.
Scindo keeps that context in one place: the channels, tasks and documents your team works in, plus the decisions it saves as it goes. Adding Scindo to Claude lets Claude ask that memory a question, cite the source, and save a new decision back into it.
Add Scindo in Claude
Works in Claude on the web, in the desktop app and on mobile.
- In Claude, open Settings → Connectors and click Add custom connector.
- Enter
https://app.scindo.one/api/mcpas the URL and click Connect. - Claude sends you to Scindo. Sign in, pick the workspace, and leave Also search my other workspaces on if you want answers from every workspace you belong to. Click Allow.
That's it. Claude is connected. There is no key to copy: your approval creates one for you, and you can see it, and revoke it, in Scindo under Settings → API Keys. Revoking it disconnects Claude.
What Claude can do once connected
Claude sees only what you can see: public channels, private channels you belong to, task threads, workspace documents and your own private documents. Direct messages are never included.
| Ask Claude | What happens |
|---|---|
| "What did we decide about the onboarding wizard?" | ask_scindo answers from your documents and chat history and cites each source |
| "Save that decision to Scindo" | save_to_knowledge_base writes a document, owned by you, visible to the workspace unless you say private |
| "What did I share last week?" | search_messages and search_knowledge_base find it; read_document reads a document in full |
| "What's open on the migration task?" | list_tasks and read_task |
The read tools run without asking you each time. Saving a document asks first.
Claude Code, Cursor and other agents
Claude Code can sign in the same way:
claude mcp add --transport http scindo https://app.scindo.one/api/mcp
Cursor, Windsurf and any client that takes an HTTP server with headers use an API key instead. Create one in Scindo under Settings → API Keys and paste the config block from Settings → Model. The full tool list and the per-client setup are in the app's help under MCP Integrations.
Why this matters
A coding agent is only as good as what it knows about your team. Pasting context into it is a chore you repeat every day, and it still misses the decision made while you were out. When your working chat lives in Scindo, Claude reads it, and what Claude helps you decide goes back in. You stop re-explaining your own project to your own tools.