# emem MCP server

> Read signed, citable facts about physical places and share them between agents as verifiable tokens.

- Listing: https://mcp.tc/i/emem
- Connect: use the server's own URL `https://emem.dev/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [AI & Machine Learning](https://mcp.tc/c/ai-ml)
- Vendor: Vortx-AI
- Homepage: <https://emem.dev>
- Repository: <https://github.com/Vortx-AI/emem>
- Package: oci `ghcr.io/vortx-ai/emem:latest`

## About

emem is a shared memory for AI agents, filled with satellite, elevation, water, air quality and other geospatial readings. Each place gets one address (cell64) and each observation is a signed fact with a content hash, so two agents can cite the same fact and check the signature without trusting each other. Tools cover place lookup, fact recall, entity identities, citation tokens, receipt verification, contradiction scans and similarity search.

The hosted endpoint at emem.dev/mcp uses streamable HTTP and needs no sign-in or API key for reads. Writes to shared spaces are tiered and need a signature. The server also ships as a Docker image (ghcr.io/vortx-ai/emem) and exposes a short tool list plus emem\_tools to discover the rest.

## What it can do

- Resolve a place name or coordinates to a canonical cell64 address
- Recall signed facts for a place and band, with auto-materialization
- Mint and resolve emem:fact: citation tokens
- Verify receipts and check claimed values against signed facts
- Scan for disagreement between attesters on the same place and band
- Mint and resolve canonical entity identities for real-world objects
- Find similar places by embedding
- Ask free-text questions about a location

## Tools (18)

- `emem_entity`: Mint or get a canonical shared identity for a real-world object.
- `emem_locate`: Resolve a place to a cell64 address and list the bands available there. (read-only)
- `emem_recall`: Read signed facts at a cell, materializing them on a miss.
- `emem_memory_token`: Compose an emem:fact: citation handle for a signed fact. (read-only)
- `emem_memory_token_resolve`: Dereference a memory token to its value, unit, band and signed fact. (read-only)
- `emem_verify_receipt`: Verify a signed ed25519 receipt server-side. (read-only)
- `emem_memory_contradictions`: Find places where independent attesters signed different values. (read-only)
- `emem_guard_verdict`: Check whether emem citations in a draft text resolve and verify. (read-only)
- `emem_tools`: List the full tool surface, search it, or get one tool's schema. (read-only)
- `emem_ask`: Answer a free-text question about a location from signed receipts.
- `search`: Search signed facts for a place and return them as citable results.
- `fetch`: Open a search result, fact citation or cell handle and read the signed record.
- `emem_echo_verify`: Compare a value you plan to publish with the signed fact it cites. (read-only)
- `emem_memory_bundle`: Compose several facts into one signed bundle envelope.
- `emem_entity_resolve`: Resolve a phrase or entity token to ranked canonical objects. (read-only)
- `emem_entity_link`: Record a signed claim that a label or external ID denotes an object.
- `emem_find_similar`: Find nearest-neighbour cells by embedding using cosine or hamming scoring.
- `emem_intent`: Describe an intent as a typed object and get the executed result.

## Example prompts

- "Has the area around 45.434, 12.323 flooded historically? Cite the signed facts."
- "Give me a citation token for the NDVI reading near Mount Fuji."
- "Verify that this emem:fact token matches the value I am about to report."
- "Find places similar to this farm plot and show the cell addresses."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http emem https://emem.dev/mcp
```

2. Start Claude Code and type `/mcp`. **emem** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **emem** and paste this URL:

```url
https://emem.dev/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=emem&connectorUrl=https%3A%2F%2Femem.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://emem.dev/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://emem.dev/mcp` as the server URL and choose **No authentication**.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=emem&config=eyJ1cmwiOiJodHRwczovL2VtZW0uZGV2L21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "emem": {
      "url": "https://emem.dev/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=emem&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Femem.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"emem","type":"http","url":"https://emem.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "emem": {
      "serverUrl": "https://emem.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add emem --url https://emem.dev/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.emem]
url = "https://emem.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http emem https://emem.dev/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://emem.dev/mcp`.

## Details

- Server version: 2.4.2
- MCP protocol version: 2025-11-25
- Last checked: 2026-10-04 (reachable)
- Listed: 2026-10-04
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/emem (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report