The remote MCP server. No local install.

The endpoint

https://mcp.octamem.com

Authentication is a bearer token passed via the Authorization header. Get one from platform.octamem.com. The same key works for REST, SDKs, and MCP, pick whichever interface fits your runtime.

Exposed tools

The MCP server exposes four tools. They map one-to-one to the REST endpoints, so anything you build against MCP is portable to direct HTTP later.

// Tools exposed by the OctaMem MCP server.

remember({
  content: string,
  type?: "semantic" | "episodic" | "procedural",
  scope?: string,
  sources?: string[],
}) -> { id: string }

recall({
  query: string,
  scope?: string,
  types?: ("semantic" | "episodic" | "procedural")[],
  since?: string, // ISO-8601
  limit?: number,
}) -> { records: Record[], context: { as_system_prompt: string } }

forget({
  ids: string[],
}) -> { deleted: number }

account({}) -> { plan, storage, rate_limits, ... }

Connect Claude Desktop / Claude.ai

Claude has first-class support for remote MCP servers. The shortest path:

• Open Settings → Connectors.
• Add an MCP connector.
• URL: https://mcp.octamem.com
• Auth: bearer token oct_live_...

See the per-client guides for screenshots and the older config-file flow: Claude Desktop · Claude.ai (web).

Connect Cursor

Cursor accepts a remote MCP server entry in its mcp.json. See the Cursor guide for the full snippet.

{
  "mcpServers": {
    "octamem": {
      "url": "https://mcp.octamem.com",
      "auth": { "type": "bearer", "token": "$OCTA_API_KEY" }
    }
  }
}

Connect a custom MCP client

Any MCP-spec-compliant client can connect. We recommend the official Python or TypeScript SDK if you’re building from scratch. See MCP client (Python) for a worked example.