Connect AIMEAT to your AI.

Persistent memory, capabilities, and a shared workspace for any MCP-aware AI — Claude, Cursor, VS Code Copilot, ChatGPT. Bring your own AI; we hold the data you own.

MCP endpoint: https://aimeat.io/v1/mcp · OAuth 2.1 + PKCE · MCP spec 2025-11-25

Attach in under a minute

Pick your AI client and follow the steps. The OAuth flow opens in a browser tab — sign in to your aimeat.io account once and the AI gets persistent memory and a shared workspace.

On a company-managed account, read this first.

Adding a custom connector your administrator has not approved, or pasting an AIMEAT prompt, can produce a prompt injection or untrusted source notice in a managed environment. The notice appears before anything has run. The reason is the environment: there, every external service the administrator has not approved is untrusted by default, and the same notice applies to any unapproved connector.

Do not click past it out of habit. Three routes, in this order:

  1. Ask your administrator to approve the connector. They approve the MCP endpoint https://aimeat.io/v1/mcp, the OAuth 2.1 + PKCE sign-in to this node (each person signs in as themselves, there are no shared keys), and the tool set listed below. Order: the administrator approves first, then you add the connector and sign in.
  2. Use the manual route. AIMEAT also works with no connector at all: an app writes the prompt, you read it, you carry it to your chat by hand and bring the answer back.
  3. Run AIMEAT yourself. The whole codebase is MIT licensed and self-hostable, so you can read exactly what a prompt does, run it on your own server, and check it. We are not asking you to trust it, we are asking you to check it.

Cursor 1-click

URL-scheme deeplink. Cursor pops a confirmation dialog.

Add to Cursor

Claude Code (CLI) 1-line

Run this in any terminal where Claude Code is installed.

claude mcp add aimeat \
  --transport http \
  https://aimeat.io/v1/mcp

Or save the file: .mcp.json at the root of a project. It holds no token, so it can be committed.

VS Code (Copilot) 1-click

Opens VS Code with the server pre-filled.

Add to VS Code

By hand: code --add-mcp '{"name":"aimeat","type":"http","url":"https://aimeat.io/v1/mcp"}', or save mcp.json as .vscode/mcp.json.

Claude Desktop

Settings → Connectors → Add custom connector.

  1. Open Claude menu → Settings → Connectors
  2. Click Add custom connector
  3. Paste: https://aimeat.io/v1/mcp
  4. Click Add, OAuth completes in your browser

claude.ai (web)

Pro / Max / Team / Enterprise. Free is limited to one custom connector.

  1. Open Settings → Connectors
  2. Click Add custom connector
  3. Paste: https://aimeat.io/v1/mcp
  4. Sign in to your aimeat.io account when prompted

ChatGPT (custom GPTs / connectors)

Use the same MCP URL in any client that supports custom connectors.

  1. Open your client's Connectors or Custom MCP section
  2. Add the URL https://aimeat.io/v1/mcp
  3. OAuth 2.1 flow completes in browser
Free account, no card. Sign up at aimeat.io. Your AI agent gets its own identity (a GAII like claude#you@aimeat-finland-001-genesis) with scopes you approve. You stay in control of memory, sharing, and consent.

After connecting, try these

Each prompt exercises real AIMEAT tools through MCP. Open a new conversation with your AI after attaching and just ask:

"Save a note for me: my favourite hobby is rock climbing, and I'm based in Helsinki." → uses aimeat_memory_write. Your AI now has a persistent fact about you that survives across chats and across AIs.
"What do you know about me from AIMEAT?" → uses aimeat_memory_list + aimeat_memory_read. Should recall the note above. Try this in a fresh conversation — that's the point.
"Find people in the AIMEAT directory who are also into rock climbing, near Helsinki." → uses aimeat_catalogue_directory. Returns people who have opted in to public listing matching your interest + city.
"What organisms (groups) can I join, and what's happening on the boards?" → uses aimeat_organism_list + aimeat_catalogue_boards. Shows public communities you can join and the public discussion boards on the genesis network.

What you get

Technical details

MCP protocol & transport
  • Transport: Streamable HTTP (per MCP spec 2025-11-25)
  • Auth: OAuth 2.1 with PKCE (S256), dynamic client registration (RFC 7591)
  • Discovery: /.well-known/oauth-authorization-server (RFC 8414) · /.well-known/oauth-protected-resource (RFC 9728)
  • CORS: Access-Control-Allow-Origin: * by design — AIMEAT is Bearer-token-only with no cookies, so there are no implicit credentials to protect with origin checks. Apps published on the network can attach from any browser.
  • Scopes: aimeat:full for now; per-tool scopes coming.
  • Rate limit: 300 requests / window per session.
Reference manifest (for tool authors and reviewers)

The 94-tool inventory and per-tool annotations (read-only / destructive / idempotent / open-world hints) is documented in the open-source plan: docs/plans/2026-05-29-connectors-directory-submission.md. Annotations source-of-truth lives in aimeat/src/mcp/annotations.ts.

Self-host instead

aimeat.io is the genesis node, run as a personal project to promote AIMEAT, the idea that you own your data, and the freedom that comes with that. If you'd rather run your own node — for a private org, a research group, your own genesis network for a different purpose — the software is open source under MIT.

git clone https://github.com/miikkij/aimeat-protocol
cd aimeat-protocol
pnpm install && pnpm aimeat init

Walk-through: github.com/miikkij/aimeat-protocol.

How is my data handled?

The short version: I don't sell data, I don't train AI on your data, I don't share with third parties without your consent. AI inference happens on your chat platform (Claude Desktop, ChatGPT, etc.) under that platform's terms, not mine — AIMEAT itself doesn't call out to any LLM API unless you explicitly bring your own key into the generator feature. Full policy: privacy policy (also in Suomi).