@triedotdev/mcp 1.0.170 → 1.0.172

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +19 -19
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,9 +1,22 @@
1
- # Trie Agent
1
+ # Trie MCP
2
2
 
3
- **Cloud context bridge for Cursor and Claude Code.** Connects AI assistants to your Trie cloud workspace—signals, documents, ledger, and graph—so agents have the right context before editing.
3
+ **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.
4
4
 
5
5
  [![Download Workspace](https://img.shields.io/badge/Download-Trie%20Workspace-blue)](https://www.trie.dev) [![Follow on X](https://img.shields.io/badge/Follow-@louiskishfy-1DA1F2?logo=x)](https://x.com/louiskishfy)
6
6
 
7
+ ## What is Trie?
8
+
9
+ [Trie](https://trie.dev) 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.
10
+
11
+ ## How it works with trie.dev
12
+
13
+ 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.
14
+
15
+ - **Accounts**: Sign up at [trie.dev](https://trie.dev). Free accounts are available.
16
+ - **Teams**: If you're on a team, `trie teams list` and `trie teams switch <teamId>` let you choose which workspace the MCP uses.
17
+ - **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.
18
+ - **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.
19
+
7
20
  ## Quick Start
8
21
 
9
22
  ### Install
@@ -18,7 +31,7 @@ npm install -g @triedotdev/mcp
18
31
  trie login
19
32
  ```
20
33
 
21
- This opens a browser to authorize the CLI with your Trie account. After login, the MCP server can access your team's cloud context.
34
+ 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.
22
35
 
23
36
  ### MCP Setup (Cursor / Claude Code)
24
37
 
@@ -56,7 +69,7 @@ If you use `npx` instead of a global install:
56
69
  trie init
57
70
  ```
58
71
 
59
- This adds Cursor rules and CLAUDE.md guidance so agents call `trie_check_file` before editing files and read `trie://context` at conversation start.
72
+ 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.
60
73
 
61
74
  ## CLI Commands
62
75
 
@@ -88,24 +101,11 @@ This adds Cursor rules and CLAUDE.md guidance so agents call `trie_check_file` b
88
101
  | `trie://context` | Consolidated context with hot zones and active signals |
89
102
  | `trie://graph` | Raw ANT graph from cloud |
90
103
 
91
- **Usage:** Agents should read `trie://context` at conversation start and call `trie_check_file` before editing high-risk files.
104
+ **Usage:** Have your AI assistant read `trie://context` at conversation start and call `trie_check_file` before editing high-risk files.
92
105
 
93
106
  ## Configuration
94
107
 
95
- Auth and config are stored locally (keychain-backed where available). The API base URL defaults to `https://trie-api.vercel.app` and can be overridden with `TRIE_API_BASE_URL`.
96
-
97
- ## Development
98
-
99
- ```bash
100
- npm install
101
- npm run build
102
- npm test
103
- ```
104
-
105
- **Before submitting:**
106
- - Tests pass (`npm test`)
107
- - Typecheck passes (`npm run typecheck`)
108
- - Lint passes (`npm run lint`)
108
+ Auth tokens and account config are stored locally in `~/.trie/`, keychain-backed where available.
109
109
 
110
110
  ## License
111
111
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@triedotdev/mcp",
3
- "version": "1.0.170",
3
+ "version": "1.0.172",
4
4
  "description": "Trie cloud context bridge for Cursor and Claude Code.",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",