MCP memory server
Model Context Protocol (MCP) lets an agent call tools over a standard transport. A memory server is an MCP endpoint that stores and returns durable context.
Archilas exposes https://www.archilas.com/api/mcp. Compatible clients include Cursor, Claude Code, ChatGPT, and Codex. Clients add the URL only and sign in with OAuth. Use OAuth for this setup; no API key is needed. Add only the MCP URL, then sign in when the client asks.
Claude Code
Shell
claude mcp add --scope user --transport http archilas https://www.archilas.com/api/mcpCursor
Put this in ~/.cursor/mcp.json (or your team MCP config), then complete OAuth when prompted.
mcp.json
{
"mcpServers": {
"archilas": {
"url": "https://www.archilas.com/api/mcp"
}
}
}What the server is for
- Ask for current decisions, people, and dates from connected tools.
- Remember and forget notes when you choose.
- Keep memory private to the workspace that owns it.
Synthetic walkthrough
Synthetic. Not a recorded session.
- Connect GitHub and Slack in Archilas Connect.
- In Claude Code, run the mcp add command above and finish OAuth.
- Ask what the current release blocker is. Expect a short answer with sources when the notes support it, or a clear abstain when they do not.
Questions
- Do I put an API key in the MCP config?
- Use OAuth for this setup; no API key is needed. Add only the URL and sign in when the client asks.
- Where are full setup steps?
- See the Docs page for Claude, Cursor, Codex, ChatGPT custom connectors, and the REST API.