@debatetalk/mcp 1.1.0 → 1.1.2

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "debatetalk",
3
3
  "description": "Run structured multi-model AI debates from your AI assistant. Multiple models argue independently, deliberate, and converge on a 4-part synthesis: Strong Ground, Fault Lines, Blind Spots, and Your Call.",
4
- "version": "1.1.0",
4
+ "version": "1.1.2",
5
5
  "author": {
6
6
  "name": "DebateTalk",
7
7
  "email": "support@debatetalk.ai"
package/README.md CHANGED
@@ -1,11 +1,21 @@
1
1
  # DebateTalk MCP
2
2
 
3
+ [![npm version](https://img.shields.io/npm/v/@debatetalk/mcp.svg)](https://www.npmjs.com/package/@debatetalk/mcp)
4
+ [![npm downloads](https://img.shields.io/npm/dm/@debatetalk/mcp.svg)](https://www.npmjs.com/package/@debatetalk/mcp)
5
+ [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE)
6
+
3
7
  > Official MCP server and CLI for [DebateTalk](https://debatetalk.ai) — run structured multi-model AI debates from your AI assistant or terminal.
4
8
 
5
9
  DebateTalk makes multiple AI models argue a question independently, challenge each other's reasoning, and converge on a structured synthesis: **Strong Ground, Fault Lines, Blind Spots, and Your Call.**
6
10
 
7
11
  ---
8
12
 
13
+ ## Demo
14
+
15
+ > Video walkthrough coming soon
16
+
17
+ ---
18
+
9
19
  ## Features
10
20
 
11
21
  - **MCP server** — connect Claude Desktop, Cursor, or any MCP-compatible client to DebateTalk
@@ -14,6 +24,8 @@ DebateTalk makes multiple AI models argue a question independently, challenge ea
14
24
  - **Cost & share links** — every debate shows cost and a shareable URL
15
25
  - **5 tools:** `run_debate`, `get_model_status`, `recommend_models`, `estimate_cost`, `get_history`
16
26
 
27
+ > **Try without an API key** — `dt models` and `dt recommend` work instantly, no signup needed. See which models are online and get a recommended panel for your question before committing to a plan.
28
+
17
29
  ---
18
30
 
19
31
  ## Quickstart
@@ -96,6 +108,18 @@ MCP clients read the tool description to decide when to call it — no exact phr
96
108
 
97
109
  Claude will also invoke it proactively for high-stakes decisions where a single AI answer is insufficient.
98
110
 
111
+ **Example — Cursor:**
112
+
113
+ Ask Cursor's AI chat: *"use the run_debate tool — should we switch from REST to GraphQL?"*
114
+
115
+ Cursor calls the MCP tool, streams progress, and returns the full synthesis inline in your chat.
116
+
117
+ **Example — Cline (VS Code):**
118
+
119
+ In Cline's agent chat: *"debate: is our current auth middleware secure enough for SOC 2?"*
120
+
121
+ Cline detects the `run_debate` tool from the MCP server and runs the debate. Results appear in the Cline output panel.
122
+
99
123
  ---
100
124
 
101
125
  ### CLI
@@ -117,6 +141,38 @@ export DEBATETALK_API_KEY=dt_your_key_here
117
141
  dt debate "Should we adopt microservices?"
118
142
  ```
119
143
 
144
+ Example output:
145
+
146
+ ```
147
+ - Starting debate…
148
+ ✔ Debate complete
149
+
150
+ "Should we adopt microservices?"
151
+ Cost: $0.0842
152
+
153
+ ━━━ STRONG GROUND ━━━
154
+ 1. Microservices suit orgs with 50+ engineers and distinct team boundaries
155
+ 2. Monoliths are simpler to operate at small scale
156
+ 3. Migration costs are consistently underestimated
157
+
158
+ ━━━ FAULT LINES ━━━
159
+ 1. If teams need independent deploy cycles, then microservices — otherwise monolith
160
+ 2. If operational maturity is low, then monolith — otherwise microservices are viable
161
+ 3. If data consistency is critical, then monolith avoids distributed transaction pain
162
+
163
+ ━━━ BLIND SPOTS ━━━
164
+ 1. Cost of distributed tracing and observability tooling
165
+ 2. Team cognitive load increases with service count
166
+ 3. Shared database patterns can bridge the gap
167
+
168
+ ━━━ YOUR CALL ━━━
169
+ 1. Do you have dedicated platform engineering?
170
+ 2. Are teams already blocked on shared deploy cycles?
171
+ 3. Can you afford 6+ months of migration investment?
172
+
173
+ 🔗 https://console.debatetalk.ai/share/a1b2c3d4-5678-90ab-cdef-1234567890ab
174
+ ```
175
+
120
176
  **Check which models are online:**
121
177
  ```bash
122
178
  dt models
@@ -194,18 +250,6 @@ Public tools (`get_model_status`, `recommend_models`) work without an API key.
194
250
 
195
251
  ---
196
252
 
197
- ## Plans & Limits
198
-
199
- | Plan | Debates/day | API keys | Debaters |
200
- |------|-------------|----------|---------|
201
- | Free | 5 | — | 3 |
202
- | Pro | Unlimited | 2 | 5 |
203
- | Enterprise | Unlimited | Unlimited | 10 |
204
-
205
- [Full pricing →](https://debatetalk.ai/resources/plans-and-limits)
206
-
207
- ---
208
-
209
253
  ## Development
210
254
 
211
255
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@debatetalk/mcp",
3
- "version": "1.1.0",
3
+ "version": "1.1.2",
4
4
  "description": "Official MCP server and CLI for DebateTalk — run structured multi-model AI debates from your AI assistant or terminal.",
5
5
  "keywords": [
6
6
  "mcp",
@@ -8,7 +8,15 @@
8
8
  "debate",
9
9
  "debatetalk",
10
10
  "claude",
11
- "llm"
11
+ "llm",
12
+ "multi-model",
13
+ "consensus",
14
+ "deliberation",
15
+ "model-council",
16
+ "multi-llm",
17
+ "structured-output",
18
+ "ai-council",
19
+ "model-comparison"
12
20
  ],
13
21
  "homepage": "https://debatetalk.ai",
14
22
  "bugs": "https://github.com/DebateTalk-AI/mcp/issues",