coherence-mcp-server 0.3.0 → 0.3.1
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.
- package/README.md +81 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -123,6 +123,37 @@ Point your MCP client at `npx coherence-mcp-server` via stdio transport.
|
|
|
123
123
|
|
|
124
124
|
---
|
|
125
125
|
|
|
126
|
+
## CLI equivalent
|
|
127
|
+
|
|
128
|
+
The Coherence CLI (`npm i -g coherence-cli`) provides the same capabilities as the MCP tools, plus additional commands. Here is the mapping:
|
|
129
|
+
|
|
130
|
+
| MCP Tool | CLI Command |
|
|
131
|
+
|----------|------------|
|
|
132
|
+
| `coherence_list_ideas` | `cc ideas` |
|
|
133
|
+
| `coherence_get_idea` | `cc idea <id>` |
|
|
134
|
+
| `coherence_idea_progress` | `cc idea <id>` (includes progress) |
|
|
135
|
+
| `coherence_select_idea` | `cc ideas` (with temperature flag) |
|
|
136
|
+
| `coherence_showcase` | `cc ideas` (showcase view) |
|
|
137
|
+
| `coherence_resonance` | `cc resonance` |
|
|
138
|
+
| `coherence_list_specs` | `cc specs` |
|
|
139
|
+
| `coherence_get_spec` | `cc spec <id>` |
|
|
140
|
+
| `coherence_list_lineage` | `cc lineage` |
|
|
141
|
+
| `coherence_lineage_valuation` | `cc lineage <id> valuation` |
|
|
142
|
+
| `coherence_list_providers` | `cc providers` |
|
|
143
|
+
| `coherence_link_identity` | `cc identity link <provider> <handle>` |
|
|
144
|
+
| `coherence_lookup_identity` | `cc identity lookup <provider> <handle>` |
|
|
145
|
+
| `coherence_get_identities` | `cc identity` |
|
|
146
|
+
| `coherence_record_contribution` | `cc contribute` |
|
|
147
|
+
| `coherence_contributor_ledger` | `cc contributor <id> contributions` |
|
|
148
|
+
| `coherence_status` | `cc status` |
|
|
149
|
+
| `coherence_friction_report` | `cc friction` |
|
|
150
|
+
| `coherence_list_change_requests` | `cc governance` |
|
|
151
|
+
| `coherence_list_federation_nodes` | `cc nodes` |
|
|
152
|
+
|
|
153
|
+
The CLI also includes additional commands not available via MCP: `cc news`, `cc treasury`, `cc assets`, `cc services`, `cc trace`, `cc diag`, and more. Run `cc help` for the full list of 54 commands.
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
126
157
|
## Example conversations
|
|
127
158
|
|
|
128
159
|
Once connected, you can ask your agent things like:
|
|
@@ -155,7 +186,56 @@ Payouts are weighted by coherence. Higher-quality work earns proportionally more
|
|
|
155
186
|
| Variable | Default | Description |
|
|
156
187
|
|----------|---------|-------------|
|
|
157
188
|
| `COHERENCE_API_URL` | `https://api.coherencycoin.com` | API base URL. Override to point at a local node. |
|
|
158
|
-
| `COHERENCE_API_KEY` | *(none)* |
|
|
189
|
+
| `COHERENCE_API_KEY` | *(none)* | API key for write operations. See below for what requires a key and how to get one. |
|
|
190
|
+
|
|
191
|
+
### What requires an API key?
|
|
192
|
+
|
|
193
|
+
**No key needed (read-only):** Browse ideas, search specs, view lineage, check contributor ledgers, see federation nodes, read coherence scores, view governance proposals.
|
|
194
|
+
|
|
195
|
+
**Key needed (write operations):** Update idea status, record contributions, link identities, create specs, vote on governance proposals, manage federation nodes, submit news sources.
|
|
196
|
+
|
|
197
|
+
Most users start without a key — exploring ideas, reading specs, checking who's contributing. You only need a key when you're ready to actively contribute.
|
|
198
|
+
|
|
199
|
+
### How to get an API key
|
|
200
|
+
|
|
201
|
+
Run the interactive setup:
|
|
202
|
+
|
|
203
|
+
```bash
|
|
204
|
+
npx coherence-cli
|
|
205
|
+
# then: cc setup
|
|
206
|
+
```
|
|
207
|
+
|
|
208
|
+
This walks you through:
|
|
209
|
+
1. Choose a contributor name
|
|
210
|
+
2. Link an identity (GitHub, Discord, Ethereum, etc.)
|
|
211
|
+
3. The system generates an API key tied to your identity
|
|
212
|
+
|
|
213
|
+
Your key is stored locally in `~/.coherence-network/config.json` and used automatically by both the CLI and MCP server.
|
|
214
|
+
|
|
215
|
+
**Manual setup** (if you already have a key):
|
|
216
|
+
|
|
217
|
+
```bash
|
|
218
|
+
export COHERENCE_API_KEY="your-key-here"
|
|
219
|
+
npx coherence-mcp-server
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
Or in your MCP config:
|
|
223
|
+
|
|
224
|
+
```json
|
|
225
|
+
{
|
|
226
|
+
"mcpServers": {
|
|
227
|
+
"coherence-network": {
|
|
228
|
+
"command": "npx",
|
|
229
|
+
"args": ["coherence-mcp-server"],
|
|
230
|
+
"env": {
|
|
231
|
+
"COHERENCE_API_KEY": "your-key-here"
|
|
232
|
+
}
|
|
233
|
+
}
|
|
234
|
+
}
|
|
235
|
+
}
|
|
236
|
+
```
|
|
237
|
+
|
|
238
|
+
Source code: [github.com/seeker71/Coherence-Network/mcp-server](https://github.com/seeker71/Coherence-Network/tree/main/mcp-server)
|
|
159
239
|
|
|
160
240
|
---
|
|
161
241
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "coherence-mcp-server",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"description": "MCP server for the Coherence Network \u2014 20 typed tools for AI agents to browse ideas, trace value chains, link identities, and record contributions. Works with Claude, Cursor, Windsurf, and any MCP client.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|