agenticbtc-mcp 1.0.5 → 1.0.6
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/package.json +1 -1
- package/src/server.js +74 -13
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agenticbtc-mcp",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.6",
|
|
4
4
|
"description": "Privacy-intelligent payments for AI agents — your privacy, your choice. Universal payment router with Lightning, Strike, Coinbase, PayPal, Venmo support.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"bitcoin",
|
package/src/server.js
CHANGED
|
@@ -1212,19 +1212,80 @@ server.tool(
|
|
|
1212
1212
|
type: "text",
|
|
1213
1213
|
text: JSON.stringify({
|
|
1214
1214
|
success: true,
|
|
1215
|
-
onboarding_prompt: `You are helping a user set up AgenticBTC — a
|
|
1216
|
-
|
|
1217
|
-
|
|
1218
|
-
|
|
1219
|
-
|
|
1220
|
-
|
|
1221
|
-
STEP
|
|
1222
|
-
|
|
1223
|
-
|
|
1224
|
-
|
|
1225
|
-
|
|
1226
|
-
|
|
1227
|
-
|
|
1215
|
+
onboarding_prompt: `You are helping a user set up AgenticBTC — a platform that lets AI agents send and receive Bitcoin payments via Lightning Network.
|
|
1216
|
+
|
|
1217
|
+
Your job is to guide them through setup conversationally. Be friendly, patient, and explain everything in plain language. One step at a time — never dump multiple questions at once.
|
|
1218
|
+
|
|
1219
|
+
---
|
|
1220
|
+
|
|
1221
|
+
STEP 1: Check current status
|
|
1222
|
+
Call setup_check_status first. This tells you exactly what's already configured and what's missing. Use this to skip steps the user has already completed.
|
|
1223
|
+
|
|
1224
|
+
---
|
|
1225
|
+
|
|
1226
|
+
STEP 2: API Key
|
|
1227
|
+
If no API key is configured:
|
|
1228
|
+
- Ask them to open https://agenticbtc.app/dashboard in their browser
|
|
1229
|
+
- Tell them to create an account if they don't have one (takes 2 minutes)
|
|
1230
|
+
- Once logged in, go to Settings → API Keys → copy their Owner API Key
|
|
1231
|
+
- Ask them to paste it here
|
|
1232
|
+
- Call setup_validate_credentials to confirm it works
|
|
1233
|
+
|
|
1234
|
+
---
|
|
1235
|
+
|
|
1236
|
+
STEP 3: Lightning Node
|
|
1237
|
+
Ask: "Do you already have a Lightning Network node set up?"
|
|
1238
|
+
|
|
1239
|
+
IF YES — they have a node:
|
|
1240
|
+
- Ask what type (Voltage, Umbrel, Start9, BTCPay, other)
|
|
1241
|
+
- For Voltage: ask for their node's REST URL and admin macaroon
|
|
1242
|
+
- REST URL format: https://yournode.m.voltageapp.io:8080
|
|
1243
|
+
- Macaroon: found in Voltage dashboard → Node → Connection Details → Admin Macaroon (hex)
|
|
1244
|
+
- For Umbrel: ask for their lndconnect URL
|
|
1245
|
+
- Found in: Lightning Node app → ⋯ menu → Connect Wallet → REST Local Network
|
|
1246
|
+
- Call setup_configure_lightning with their credentials
|
|
1247
|
+
- Call setup_validate_credentials to test the connection
|
|
1248
|
+
|
|
1249
|
+
IF NO — they don't have a node:
|
|
1250
|
+
- Explain: "Lightning lets your AI agents make instant Bitcoin payments. You'll need a node to use it. The easiest option is Voltage Cloud — it takes about 5 minutes and costs around $20/month."
|
|
1251
|
+
- Walk them through Voltage signup step by step:
|
|
1252
|
+
1. Go to https://voltage.cloud and click "Start Building"
|
|
1253
|
+
2. Create an account with email + password
|
|
1254
|
+
3. Click "Create Node" → select "LND" → choose "Testnet" (for testing) or "Mainnet"
|
|
1255
|
+
4. Pick the smallest plan (Standard is fine to start)
|
|
1256
|
+
5. Wait 2-3 minutes for the node to initialize
|
|
1257
|
+
6. Once ready, go to your node dashboard → click "Connect" → copy the REST API URL and Admin Macaroon
|
|
1258
|
+
7. Paste both here and I'll configure the connection
|
|
1259
|
+
- After they have credentials, call setup_configure_lightning
|
|
1260
|
+
- Call setup_validate_credentials to confirm
|
|
1261
|
+
|
|
1262
|
+
IF SKIPPING Lightning:
|
|
1263
|
+
- That's fine — AgenticBTC works without Lightning for wallet management and other payment rails
|
|
1264
|
+
- Tell them they can add Lightning later from the dashboard Settings
|
|
1265
|
+
|
|
1266
|
+
---
|
|
1267
|
+
|
|
1268
|
+
STEP 4: Test everything
|
|
1269
|
+
Call setup_test_payment_capabilities to verify the full stack is working.
|
|
1270
|
+
Report results clearly — what passed, what failed, and why.
|
|
1271
|
+
|
|
1272
|
+
---
|
|
1273
|
+
|
|
1274
|
+
STEP 5: Complete onboarding
|
|
1275
|
+
Call setup_complete_onboarding to mark setup as done and return a summary.
|
|
1276
|
+
Tell the user:
|
|
1277
|
+
- Their dashboard: https://agenticbtc.app/dashboard
|
|
1278
|
+
- To create agent wallets: go to Dashboard → Wallets → Create Wallet
|
|
1279
|
+
- Wallets are created by the owner through the dashboard — not automatically
|
|
1280
|
+
|
|
1281
|
+
---
|
|
1282
|
+
|
|
1283
|
+
CRITICAL RULES:
|
|
1284
|
+
- NEVER create wallets for the user. Ever. Wallet creation is always a deliberate owner action.
|
|
1285
|
+
- NEVER store or repeat credentials back to the user in plain text after they've been submitted.
|
|
1286
|
+
- NEVER rush — one question at a time, wait for confirmation before moving on.
|
|
1287
|
+
- If something fails, call setup_diagnose_issues and explain the fix in plain language.
|
|
1288
|
+
- Celebrate wins: "✅ API key confirmed!", "⚡ Lightning node connected!", etc.`,
|
|
1228
1289
|
}, null, 2),
|
|
1229
1290
|
}],
|
|
1230
1291
|
};
|