MCP and agents
Connect Claude Code, Cursor and other assistants directly to a memory or project.
Chordian exposes Model Context Protocol endpoints so an assistant can read from and write to memory without leaving the editor or chat window.
This is where a memory platform either becomes infrastructure or stays a website people occasionally visit.
Endpoints
| Endpoint | Scope |
|---|---|
/mcp/memory | A whole memory |
/mcp/space/{space_id} | One project |
Prefer the project endpoint. Scoping an assistant to one project is almost always what you want, and scope is enforced server-side from the credential rather than requested by the client.
Tools
| Tool | Purpose |
|---|---|
search | Query the memory in scope |
write | Store content |
space_get | Fetch project context — name, vault, recent topics |
conversation_history | Read prior conversations |
save_conversation | Persist a session |
append_conversation_content | Extend an existing conversation |
pages_search | Find Notes by meaning |
pages_read | Read a Note |
pages_create | Create a Note |
pages_update | Update a Note |
contradictions_list | List conflicting facts awaiting review, with both values and their sources |
contradictions_get | Get one contradiction in full |
contradictions_resolve | Resolve a contradiction: accept_incoming, keep_existing, both_valid or ignore. Write access; audit-logged |
sensitive_data_list | List passages where sensitive data was detected and masked. Masked previews only |
documents_get | Get an uploaded document's processing status. The document text is not returned |
memory_health_get | Get the latest knowledge-quality grade, its dimensions and top issues |
Read tools carry the MCP readOnlyHint; contradictions_resolve is marked destructiveHint, so clients that
honour hints ask the user before calling it. The six knowledge-quality and security tools work on shared
memories; on a dedicated or self-hosted memory box they return a clear "not available yet" error.
Connecting
The endpoint implements a full OAuth 2.1 authorization server — discovery, dynamic client registration and a consent screen. A modern MCP client discovers and completes the flow on its own:
{
"mcpServers": {
"chordian": {
"url": "https://api.chordian.ai/mcp/space/spc_7f3a91"
}
}
}The client registers itself, opens the consent screen in a browser, and stores the resulting token. Nothing is pasted.
Per-project scoping
Create a Project per codebase
One Project per repository or workstream.
Mint a scoped key per project
Give each project its own credential.
Commit the config, not the key
Reference the credential from the environment so the config can be shared without the secret.
Two projects then get two projects with no cross-talk, and revoking one does not disturb the other.
Per-project config generators in the console, and automatic session capture on disconnect, are specified but not built. Configure manually for now.
Not yet published
The MCP endpoints work and are connectable today. Chordian is not yet listed in the Claude Code, Cursor or Windsurf plugin directories — configure by URL rather than looking for a marketplace entry.