Trie MCP

CLI + MCP tools for Cursor, Claude Code, and Codex. Connect your coding assistant to Trie Memory — the voice memos, notes, and ideas you capture in Trie Microphone — so your AI can search your ledger and ANT graph while you build.

Quick Start

Install

npm install -g @triedotdev/mcp

Login

trie login

Use the same trie.dev account as Trie Microphone. One account, one Memory workspace. If you don't have one yet, create it in the app or at trie.dev, then run trie login.

MCP Setup

Cursor

Add to ~/.cursor/mcp.json (or project .cursor/mcp.json):

{
  "mcpServers": {
    "trie": {
      "command": "npx",
      "args": ["-y", "@triedotdev/mcp", "mcp"]
    }
  }
}

Claude Code

claude mcp add trie -- npx -y @triedotdev/mcp mcp

Or add to .mcp.json in your project:

{
  "mcpServers": {
    "trie": {
      "command": "npx",
      "args": ["-y", "@triedotdev/mcp", "mcp"]
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.trie]
command = "npx"
args = ["-y", "@triedotdev/mcp", "mcp"]

Global install variant

If you installed globally (npm install -g @triedotdev/mcp), replace npx -y @triedotdev/mcp mcp with just mcp.

Not signed in yet? Run trie login in a terminal, or ask your assistant to call the trie_login MCP tool.

Suggested workflow in your coding tool

At the start of a session:

Use trie_search to find what I've decided about [topic]

Or load a quick overview:

Use trie_context

Before logging a decision from your editor:

Use trie_create_note to save this insight to Memory

Optional: Cursor / Claude rules

trie init

Adds project rules that remind your assistant to call trie_context or trie_search at conversation start. Safe to skip if you prefer prompting manually.

CLI Commands

| Command | Description | |---------|-------------| | trie login | Sign in via browser (trie.dev) | | trie logout | Revoke this machine's session | | trie status | Show auth and cache stats | | trie pull ledger | Print ledger insights as JSON | | trie pull graph | Print ANT graph as JSON | | trie pull signals | Print signals feed as JSON | | trie pull documents | Print imported documents as JSON | | trie pull all | Print ledger, graph, signals, and documents | | trie lint | Run a graph health check (stale nodes, orphans) | | trie lint history | Show past lint runs | | trie settings lint [on\|off] | Toggle auto-lint at MCP startup | | trie init | Add Cursor/Claude rules for Memory-aware prompting |

MCP Tools

Primary — Memory & ideas (Microphone workflow)

| Tool | Description | |------|-------------| | trie_search | Natural-language search over your Memory, notes, and graph | | trie_ledger | Read ledger insights (memos, hypotheses, logged ideas) | | trie_graph | Read the ANT graph (actants and relationships from your notes) | | trie_context | Quick overview: graph size, recent signals, imported documents | | trie_create_note | Create a note in Memory (summarized server-side, feeds the graph) | | trie_log_to_memory | Batch-import notes or text into Memory (async, like Apple Notes import) | | trie_login | Sign in via trie.dev when tools report "Not authenticated" |

Secondary — feeds & maintenance

| Tool | Description | |------|-------------| | trie_signals | Read the signals feed (derived highlights from your Memory) | | trie_documents | Read imported documents (e.g. notes seeded from Apple Notes) | | trie_lint | Health check on your graph (stale entries, orphan nodes) | | trie_check_file | Match a file path against ledger/graph text — useful only if your Memory mentions specific files |

MCP Resources

| URI | Description | |-----|-------------| | trie://context | JSON snapshot: graph summary, recent signals, documents | | trie://graph | Raw ANT graph JSON |

Some clients cannot fetch MCP resources directly — use the trie_context or trie_graph tools instead.

Example prompts

What have I said about pricing in my Trie memos?
→ trie_search

Show the relationships between my recent ideas
→ trie_graph

Log this decision: we're targeting solo founders first
→ trie_create_note

License

MIT License — see LICENSE.