Docs

Give your agents the context

Archilas keeps what was decided, what was said in a chat, and what an agent was told and did. It then gives that context to any AI that supports MCP.

Start free, then open Connect. Create a key in the workspace. The full key is shown once. The snippets below use ak_live_… as a redaction, not a working secret.

Install

The public installer is public/install.sh on this site. It registers the hosted MCP server. Compatible with any AI that supports MCP. Cursor, Claude Code, ChatGPT, and Codex are examples.

curl -fsSL https://www.archilas.com/install.sh | sh -s -- <api-key>

MCP

The endpoint is https://www.archilas.com/api/mcp. It accepts HTTP GET, POST, and DELETE, and the OAuth metadata routes under that path. Send the workspace key as Authorization: Bearer. The same URL works for any client that can call a remote MCP server. Cursor, Claude Code, ChatGPT, and Codex are examples.

https://www.archilas.com/api/mcp

Claude Code

claude mcp add --transport http archilas https://www.archilas.com/api/mcp --header "Authorization: Bearer ak_live_…"

Cursor

Put this in ~/.cursor/mcp.json, or use the install link the workspace shows.

{
  "mcpServers": {
    "archilas": {
      "url": "https://www.archilas.com/api/mcp",
      "headers": { "Authorization": "Bearer ak_live_…" }
    }
  }
}

Codex

[mcp_servers.archilas]
url = "https://www.archilas.com/api/mcp"
http_headers = { Authorization = "Bearer ak_live_…" }

ChatGPT and other clients

Add a custom MCP connector. Paste the same URL. When the client asks for a header, send Authorization: Bearer and the workspace key. There is no separate “coming soon” client. If a client cannot add a remote MCP server, that limit is in the client, not a missing Archilas integration.

The tool the server registers includes archilas.ask (also archilas_ask). It returns context with sources. If the tool says no memory found, the agent should say it does not know.

Connectors

Slack, GitHub, Gmail, Notion, Linear, Google Calendar, Google Drive, and AI chats are the sources the product treats as connected, together with agent actions.

The connector code also implements Jira, Confluence, HubSpot, Salesforce, Pipedrive, Attio, Close, Intercom, Zendesk, and Figma. A connector can be used when its environment variables are set. Discord is not implemented: guild messages are not delivered over HTTPS in this design. Microsoft Teams is not implemented: Graph subscriptions expire too quickly for the cron this app runs. Google Drive can export Doc text when the file is a Doc. There is no separate Google Docs connector.

Gmail, Google Calendar, and Google Drive go through Composio. GitHub, Slack, Notion, and Linear use their own OAuth apps. Credentials are encrypted with AES-256-GCM before they are stored.

Memory and what changed

Each note keeps the date and where it came from. When a later decision replaces an earlier one, the older note stays and is marked replaced. Both dates remain. The context an agent receives should prefer the current note and can still show the one it replaced.

AI chats and agent actions are sources, not a second product. “Agent actions” means what the agent was told and what it did. Free includes all AI chat context, one integration, and 100 metered deliveries a month. The product calls that meter questions. Every paid plan includes all integrations: Pro ($19, 1,000 questions, 1 seat), Builder ($49, 2,500 questions, 1 seat), Studio ($99, 5,000 questions, all integrations, 3 seats), and Team ($199, 10,000 questions, all integrations, 10 seats). Checkout in the app is off.

This codebase does not train a model on workspace content. Generating an answer sends relevant notes to OpenRouter. If the notes do not support a fact, the service is built to abstain.

HTTP API

All of these require a workspace credential. Send JSON unless noted.

  • POST /api/v1/ask with { "question": "…" }. Returns answer, abstain, and sources.
  • POST /api/v1/remember with text, and optional source, tags or topic, and saidBy.
  • GET /api/v1/changes?since= returns notes and items changed since that time.
  • POST /api/hook/context with { "prompt": "…" }. A short hook that returns additional context for the prompt. An empty prompt returns an empty context.
  • POST /api/hook/remember stores a note from a hook.
  • POST /api/ingest/transcript ingests a transcript body, with a size limit enforced in the route.
  • GET /api/account/export downloads a JSON export for the signed-in member.
  • GET /api/health reports whether the app can reach its database and memory configuration.
  • POST /api/waitlist with { "email": "…" } stores a waitlist address when the store is configured.

Connector routes live under /api/integrations/<provider>/connect, callback, disconnect, and sync, plus provider webhooks. Those are for the signed-in workspace, not a public API to call with a guessed provider name.

Questions: hermes@archilas.com.