Trie MCP

CLI + MCP tools for Cursor and Claude Code. A bridge that extends your AI assistant with Trie cloud context—signals, documents, ledger, and graph—so it has the right context before editing.

What is Trie?

Trie is a product governance platform that captures governance and insights automatically from conversations, commits, design files, and support threads. It builds a shared ledger from your team's work—integrations so everyone (humans and agents) has context before shipping changes.

How it works with trie.dev

This package connects your local AI assistant (Cursor, Claude Code) to your trie.dev account. You sign in with trie login, which opens a browser to authorize the CLI. Once authenticated, the MCP server pulls context from your human and agent teams' graph on the fly—signals, documents, ledger, and graph—and exposes it as tools your AI can call while you work.

• Accounts: Sign up at trie.dev. Free accounts are available.
• Teams: If you're on a team, trie teams list and trie teams switch <teamId> let you choose which workspace the MCP uses.
• Live context: Context is fetched from your trie.dev workspace as your AI needs it—both human team activity and agent-generated insights flow into the graph in real time.
• Local storage: Auth tokens and account config (team, email) are stored in ~/.trie/ on your machine—keychain-backed where available. Cloud data (signals, graph, documents) is only held in memory during the session and never written to disk.

Quick Start

Install

npm install -g @triedotdev/mcp

Login

trie login

This opens a browser to sign in at trie.dev and authorize the CLI. After login, the MCP server can access your team's cloud context.

If you do not have a Trie account yet, create one first at trie.dev, then run trie login.

MCP Setup (Cursor / Claude Code)

Add to your MCP settings:

{
  "mcpServers": {
    "trie": {
      "command": "mcp",
      "args": [],
      "env": {}
    }
  }
}

If you use npx instead of a global install:

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

Proactive Warnings

trie init

This adds Cursor rules and CLAUDE.md guidance so your AI assistant calls trie_check_file before editing files and reads trie://context at conversation start.

CLI Commands

| Command | Description | |---------|-------------| | trie init | Add Cursor/Claude rules for proactive file checks | | trie login | Sign in via browser (OAuth) | | trie logout | Revoke session | | trie teams [list\|switch <teamId>] | List or switch teams | | trie pull [context\|graph\|signals\|documents\|ledger\|all] | Fetch cloud data (JSON) | | trie status | Show auth and cache status |

MCP Tools

| Tool | Description | |------|-------------| | trie_context | Consolidated context: hot zones, graph summary, recent signals/documents | | trie_check_file | Risk assessment for a file (incidents, alerts, decisions) | | trie_graph | Read ANT graph from cloud | | trie_signals | Read signals feed | | trie_documents | Read cloud documents | | trie_ledger | Read cloud ledger entries | | trie_search | Natural language search over cloud context |

MCP Resources

| URI | Description | |-----|-------------| | trie://context | Consolidated context with hot zones and active signals | | trie://graph | Raw ANT graph from cloud |

Usage: Have your AI assistant read trie://context at conversation start and call trie_check_file before editing high-risk files.

Configuration

Auth tokens and account config are stored locally in ~/.trie/, keychain-backed where available.

License

MIT License - See LICENSE for details.