Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AIMEAT

by miikkijversion 4.0.1i★ –iRuns in the cloud
Registry nameio.aimeat/aimeat

Install

Overview

Description from the maker (original English)

Your knowledge, agents and apps on a node you own, reached from the AI you already use.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://aimeat.io/v1/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "aimeat": {
      "url": "https://aimeat.io/v1/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "aimeat": {
      "type": "http",
      "url": "https://aimeat.io/v1/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://aimeat.io/v1/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain aimeat.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7230 servers in this category
  • Published to the registry more recently than 61% of the other 7230 servers in this category
  • Basic checks equal to or better than 100% of the other 7230 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AIMEAT safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (4.0.1) reached the registry 23 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AIMEAT

The Linux of AI: an operating system for the AI you already use, and you can build anything on it.

Keep what you know, your agents and your apps in one place you own, and use all of it from the AI you already talk to.

Tell Claude, ChatGPT, Cursor or another AI to remember something, and it is still there in the next conversation, in the next tool, and for the people and agents you choose to share it with. Your AI can also build you an app, hand work to an agent or run a task on a schedule, and all of it stays under your name. You see which AI did what, and you take its access back with one press.

AIMEAT (AI Memory Exchange and Action Transfer) is open source under the MIT licence. It runs on aimeat.io, on your own server, or on your own computer.

Try it first, without an account. The Experience Center is a free tour in English, Finnish and Spanish. It shows what AIMEAT gets done, with examples from real apps, and gives you steps to try with your own AI as you go.

Three ways in

1. Connect the AI you already use

Add this address to your AI as a connector (some tools call it a custom connector or an MCP server):

https://aimeat.io/v1/mcp

Sign in when your AI asks, and choose what it may do: read only, standard, full, or exactly the permissions you tick. Then ask it in the chat what it can do in AIMEAT.

  • The steps for each AI tool, with every field value, are on the Connect your AI page. The same table for software is served at /v1/ai-tools. Signed in, the Connect your AI page in your settings shows every connected AI and disconnects any of them.
  • AI tools on your own computer (Claude Code, Cursor, VS Code, goose, Claude Desktop) are set up with one command. It registers the tool as an agent of yours, which you approve on the Agents page, and writes the tool's MCP settings without putting the token in them:
  npx aimeat connect client claude-code --url https://aimeat.io --owner <your-handle>

The options, the guarantees and the other clients: Connecting an AI client.

  • An AI that cannot connect over MCP (a consumer Gemini app outside the United States, Copilot without Copilot Studio) still works. The page gives you a ready prompt, you run it in your own chat and paste the answer back.
  • On a company-managed AI account, a connector or a prompt can show a prompt injection warning before anything runs. What it means and what to do.

aimeat.io is the demonstration node. It is free to try and it runs for real, and the Experience Center takes you through it level by level. To keep your knowledge on a machine of your own, take the second way in.

2. Run your own node
npx aimeat init     # asks a few questions and writes .env: storage, the node's name, its keys

npx aimeat start # serves http://localhost:40050

You need Node.js 24 or later. SQLite needs no database server; PostgreSQL is the production backend. Open http://localhost:40050/: a new node shows its setup page, where you create the first account, the one that runs the node. Then connect your AI to http://localhost:40050/v1/mcp as in the first way in, or with --url http://localhost:40050.

  • On your own computer, without a terminal: the desktop app AIMEAT Personal Node for Windows, Apple-silicon Macs and Linux. It attaches the AI tools on the computer to your AIMEAT (aimeat.io or your own), and it can run a node of your own on port 41050. The installers are on the desktop-latest release. They are not code-signed yet, so Windows and macOS ask you to confirm the first launch. Details: aimeat-desktop/README.md.
  • From source or with Docker, and what to back up: Build and operate a node.
  • Every setting and where its value comes from: configuration reference.
  • Before you open a node to the internet: the deployment checklist.
  • A personal node behind a home connection, attached through a public node: the personal node guide.
  • One node for a company and the partners it approves: see For a company below.
  • If you cloned the repository and want a coding assistant to do the setup, paste startup.prompt.md into it.
3. Build on a node
  • Apps. Every node serves its app-building instructions at /v1/prompts/build-app-atelier (aimeat.io's). Describe the app to your connected AI and it builds a single HTML file and publishes it on the node, on an address of its own. App development.
  • Agents. An agent joins a node through device authorization, and the owner approves it and picks its permissions. Building an AIMEAT-compatible agent. For CrewAI there is a Python package, aimeat-crewai (pip install aimeat-crewai).
  • Ecosystem apps. A service of your own that works in its users' AIMEAT with their consent: Building an AIMEAT-compatible ecosystem app.
  • Agent platforms such as Dify, n8n or Open WebUI connect once as an MCP client of the node. The Dify walkthrough: aimeat/tools/dify-bridge/README.md.
  • The API. openapi.yaml is the contract. A running node describes itself at /llms.txt and in full at /llms-full.txt.

For a company

One node can serve a company, its staff and the partner companies it approves, and nobody else. Every setting is also on the admin Config tab, so the operator changes it without a restart. The whole recipe: a company node, step by step.

  • Sign-in with Microsoft Entra ID, limited to your own tenant and the partner tenants you list. A new account comes only through Entra or an invitation.
  • Closed to the internet. With one setting, everything on the node is hidden from people without an account.
  • Nothing becomes public without its owner. When an agent or an app tries to make something public, the owner gets a notification and approves or declines it.
  • Everyone on the node sees each other in the address book, and a colleague's first message needs no approval.
  • Classification. Content is public, internal, confidential or highly confidential. A shared place passes its classification on to what it holds, and each classification limits who may see the content and what an agent may read. (data classification)
  • The records the GDPR asks for: a record of processing for the node, each organism and each app, and data processing agreements made from what the node holds. (AI transparency and compliance)
  • AI calls that stay in Europe. The node's AI calls go only to model servers in the EU or the EEA, the United Kingdom and Switzerland, or only to the United States, or to any country. You choose, you can let each person choose, and every answer says where it was processed. The privacy page and the records of processing follow the setting. (where AI calls are processed) A node bought from the store is set up with one choice that sets all of this: EU first, EU only (speech, image generation and the free models are off) or each person's own key (AIMEAT_AI_REGION_MODE, or ai.region_mode on the Config tab).

What it does

The feature list says what a node does today, area by area, with the API route and the MCP tools for each feature. In short:

  • Your knowledge, kept and shared on your terms. Memory, files and search; organisms and workspaces where people, agents and apps work on shared records; consent and visibility on every record. (memory, organisms and workspaces, access and consent)
  • Agents that work for you. Each agent has its own identity, permissions you approve, tasks, schedules and workflows, and you can stop it at any time. Give your agents a goal in your own words: your AI plans the work, and nothing starts before you say yes. ([the agent fleet](https://

Only the beginning is shown; read the rest in the repo

Ask PopNx