AIfa Memory — MCP server

One memory for you and your AI agents. AIfa Memory is a hosted Model Context Protocol server. It connects Claude, Cursor, VS Code or any other MCP client to the memory of your AIfa account — the same memory AIfa uses when you talk to her on aifa.works, codeofdigitaleternity.com, aifa.digital and radiocode.space.

Your agent can recall what you discussed with AIfa weeks ago, save new decisions, and hand everything back to you as one Markdown file whenever you want to leave.

Endpoint   https://aifa.works/api/mcp
Transport  Streamable HTTP (JSON-RPC 2.0, stateless)
Auth       Authorization: Bearer <your key>
Version    1.7.0 · protocol 2025-06-18, 2025-03-26, 2024-11-05

This repository holds the public description of the server: connection examples, the full tool list and the registry manifest. The server itself runs on aifa.works; its code lives in the private site repository together with the database and payments. If you want a memory server you can read and run yourself, see padam-nocturne — our open-source, local-first MCP memory (one SQLite file, 8 tools).

Quick start

1. Sign in at aifa.works/mcp and create your key. One key per account.

2. Add the server to your client (examples below). Replace YOUR_AIFA_MCP_KEY with your key.

3. Ask your agent: "Search my AIfa memory for what we decided about …"

Claude Code

claude mcp add --transport http aifa-memory https://aifa.works/api/mcp --header "Authorization: Bearer YOUR_AIFA_MCP_KEY"

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "aifa-memory": {
      "url": "https://aifa.works/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_AIFA_MCP_KEY" }
    }
  }
}

VS Code — .vscode/mcp.json

{
  "servers": {
    "aifa-memory": {
      "type": "http",
      "url": "https://aifa.works/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_AIFA_MCP_KEY" }
    }
  }
}

Claude Desktop — claude_desktop_config.json

Claude Desktop connects to remote servers through mcp-remote. The header is passed without spaces inside args and the value goes into env — on Windows, spaces inside args break the header.

{
  "mcpServers": {
    "aifa-memory": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://aifa.works/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_AIFA_MCP_KEY" }
    }
  }
}

The same files are in examples/.

Related MCP server: memory-mcp

Tools

Fifteen tools. Full parameters and hints: TOOLS.md.

Memory

Account

Partner program (bringing clients to AIfa Works accessibility services)

Plans: Spark $15/month · Family Archive $100/month · Digital DNA $1,000 once per device, then $200/month. The plans tool always returns the current prices and limits.

How your data is handled

• The key decides everything. The account is taken only from the key, never from the request body. No tool takes an email or user ID as input, so one account cannot read another's memory.

• Without a key the server answers only initialize, ping and tools/list. Every tools/call without a valid key returns Unauthorized.

• Revoking a key. Signing out on all devices in your cabinet revokes it.

• Limits. 60 calls a minute per key, of them 20 searches. 30 calls a minute per address without a key. Tool answers are trimmed so that one call cannot pull a whole history; use memory_export for a full copy of your own memory.

• Permanent copy. On paid plans a copy of your conversations is stored on Arweave, encrypted with your own key; every record has its own key, so a single record can be made unreadable without touching the rest.

• Leaving. memory_export gives you everything as Markdown. You can leave whenever you want and take your memory with you.

Found a security problem? See SECURITY.md.

Registry

server.json is the manifest for the official MCP Registry (schema 2025-12-11) under the name works.aifa/aifa-memory.

Links

• Get a key and read the guide: aifa.works/mcp

• Partner program: aifa.works/partners

• Open-source local memory: padam-nocturne

• Contact: contact@codeofdigitaleternity.com

License

The documentation and configuration examples in this repository are released under the MIT License. The AIfa Memory service itself is provided by CODE Eternal LLC under the terms published on aifa.works.