MCP setup

Aago exposes a remote MCP server over Streamable HTTP. Point any MCP-compatible client at it and your agents can list, search, read, and edit your documents.

• Endpoint (production): https://aago.social/api/mcp
• Endpoint (local dev): http://localhost:3000/api/mcp
• Auth: Authorization: Bearer aago_... — your API key

Tools

documents_list, documents_search, documents_get, documents_create, documents_update, documents_archive, documents_restore, documents_duplicate, documents_favorite.

All tools are scoped to the key owner's documents.

Claude Code / Claude Desktop

{
  "mcpServers": {
    "aago": {
      "url": "https://aago.social/api/mcp",
      "headers": { "Authorization": "Bearer aago_..." }
    }
  }
}

Codex CLI

codex mcp add aago \
  --url "https://aago.social/api/mcp" \
  --header "Authorization: Bearer aago_..."

Opencode

{
  "mcp": {
    "aago": {
      "type": "remote",
      "url": "https://aago.social/api/mcp",
      "headers": { "Authorization": "Bearer aago_..." }
    }
  }
}

Hermes

Hermes speaks remote MCP over Streamable HTTP — use the same URL and header. If your build only supports stdio, wrap it:

npx -y mcp-remote https://aago.social/api/mcp \
  --header "Authorization: Bearer aago_..."

Key hygiene

Rotate your key after sharing it or on any suspicion of a leak — the old key stops working immediately, then update the header in each client. Deleting the key revokes all agent access at once.