MCP Integration

What is MCP?

The Model Context Protocol (MCP) is an open standard for exposing tools and resources to AI agents over JSON-RPC 2.0. Rather than building a bespoke SDK for every framework, MCP lets any compatible client — Claude Desktop, Cursor, LangChain, a custom agent loop — discover and call tools via a single HTTPS endpoint.

Agentverse Memory exposes all 35 memory tools over a single MCP endpoint. No SDK required, though Python and TypeScript SDKs are available for convenience.

Connection Details

Give Claude Persistent Memory in 5 Minutes

This walkthrough gives Claude Desktop access to all 35 Agentverse Memory tools — episodic, semantic, graph, procedural, working, and shared — with zero code.

{
  "mcpServers": {
    "agentverse-memory": {
      "url": "https://am-server-jbneh74b5q-uc.a.run.app/mcp",
      "headers": {
        "Authorization": "Bearer avmem_sk_your_key_here"
      }
    }
  }
}

npm install -g agentverse-memory-mcp

{
  "mcpServers": {
    "agentverse-memory": {
      "command": "npx",
      "args": ["-y", "agentverse-memory-mcp", "--agent-id", "claude-desktop"],
      "env": {
        "AVMEM_API_KEY": "avmem_sk_your_key_here"
      }
    }
  }
}

{ "status": "ok", "version": "0.1.0", "uptime_s": 12345 }

Client Configurations

{
  "mcpServers": {
    "agentverse-memory": {
      "url": "https://am-server-jbneh74b5q-uc.a.run.app/mcp",
      "headers": {
        "Authorization": "Bearer avmem_sk_your_key_here"
      }
    }
  }
}

{
  "mcpServers": {
    "agentverse-memory": {
      "url": "https://am-server-jbneh74b5q-uc.a.run.app/mcp",
      "headers": {
        "Authorization": "Bearer avmem_sk_your_key_here"
      }
    }
  }
}

{
  "agentverse-memory": {
    "serverUrl": "https://am-server-jbneh74b5q-uc.a.run.app/mcp",
    "headers": {
      "Authorization": "Bearer avmem_sk_your_key_here"
    }
  }
}

curl -X POST https://am-server-jbneh74b5q-uc.a.run.app/mcp \
  -H "Authorization: Bearer avmem_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'

curl -X POST https://am-server-jbneh74b5q-uc.a.run.app/mcp \
  -H "Authorization: Bearer avmem_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "memory_store_episode",
      "arguments": {
        "agent_id": "my-agent",
        "content": "Completed Q1 analysis for user_42."
      }
    }
  }'

All 35 MCP Tools

All tools are available at every plan tier unless noted. Graph traversal tools (memory_traverse_graph, memory_find_path) are available on all tiers including Explorer (free). See the API Reference for full parameter schemas.

Authentication

All requests must include an Authorization header:

Authorization: Bearer avmem_sk_your_key_here

export AVMEM_API_KEY="avmem_sk_your_key_here"

API keys are scoped to your account. You can issue multiple keys (one per agent, one per environment) and revoke individual keys without affecting others.

Rate Limits

Applied per API key (not per agent_id).

"Ops" are counted per MCP tool call. A memory_traverse_graph call counts as one op regardless of how many edges it traverses. When you exceed rate limits, the server returns HTTP 429 with a Retry-After header (rolling 30-day window).

Error Codes

{
  "jsonrpc": "2.0",
  "id": 3,
  "error": {
    "code": -32029,
    "message": "Rate limit exceeded",
    "data": {
      "limit": 50000,
      "used": 50001,
      "reset_at": "2026-06-14T00:00:00Z",
      "retry_after": 1814400
    }
  }
}