Lewati ke konten utama

Penyiapan agen MCP

Connect an AI client to Domestic Monero’s hosted MCP endpoint with a Profile DM_TOKEN. This page is install only.

MCP endpoint (paste this URL): https://mcp.domesticmonero.com/mcp

The host root https://mcp.domesticmonero.com is not the MCP path. Clients must use /mcp.

Prerequisites​

  1. Open the Mini App from the official bot.
  2. You can reach Profile in the Mini App.

Bot resmi: @domestic_monero_bot — Buka Mini App

Buka di Telegram
Gunakan hanya saluran resmi

Tidak ada akun dukungan terpisah, chat help desk, atau layanan pemulihan pihak ketiga untuk Domestic Monero. Pesan bot resmi saja.

Bot resmi: @domestic_monero_bot — Buka Mini App

Publish a token in Profile​

  1. Open the Mini App → Profile.
  2. Open MCP access.
  3. Publish a token. Copy it when it is shown — the full value appears once. Tokens start with dm_.
  4. Store it as DM_TOKEN. Clients send Authorization: Bearer <DM_TOKEN>.

Only one active token is allowed. To rotate, Revoke the current token, then publish again.

Telegram Mini App Profile MCP token ready modal in light theme — token value blurred; MCP URL and Setup guide (Archive) link visible; Done control.Telegram Mini App Profile MCP token ready modal in dark theme — token value blurred; MCP URL and Setup guide (Archive) link visible; Done control.
Profile → MCP access after Publish — copy the token once, note the MCP URL, open Setup guide.

Contract​

SettingValue
URLhttps://mcp.domesticmonero.com/mcp
AuthAuthorization: Bearer <DM_TOKEN>

Replace dm_YOUR_TOKEN_HERE with your published token. Never commit a real token.

Cursor​

Project file: .cursor/mcp.json — or global ~/.cursor/mcp.json.

{
"mcpServers": {
"domestic-monero": {
"url": "https://mcp.domesticmonero.com/mcp",
"headers": {
"Authorization": "Bearer dm_YOUR_TOKEN_HERE"
}
}
}
}

Fields used: url, headers.Authorization (Cursor remote MCP shape). Optional: Bearer ${env:DM_TOKEN} if the token is in your environment.

Reload MCP servers in Cursor (Customize → MCP), then run Verify below.

Claude Desktop​

Claude Desktop does not take a remote url + headers block in claude_desktop_config.json. Use a custom connector (Claude Desktop / claude.ai) with these fields:

FieldValue
MCP server URLhttps://mcp.domesticmonero.com/mcp
AuthenticationNo sign-in
Request headers → header nameAuthorization
Request headers → valueBearer dm_YOUR_TOKEN_HERE (include the Bearer prefix)

Steps: Customize → Connectors → Add custom connector → paste the URL → choose No sign-in → add the Authorization request header → save. Turn the connector on for the chat, then run Verify below.

If your plan only supports local stdio servers in claude_desktop_config.json, bridge with mcp-remote:

{
"mcpServers": {
"domestic-monero": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.domesticmonero.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer dm_YOUR_TOKEN_HERE"
}
}
}
}

Fields used: command, args (mcp-remote + --header), env.AUTH_HEADER. Keep the Authorization:${AUTH_HEADER} form with no spaces around :.

Generic HTTP​

Without a Bearer token, the server returns 401 and this JSON-RPC error:

{
"jsonrpc": "2.0",
"error": {
"code": -32001,
"message": "Authorization Bearer required (DM_TOKEN)"
},
"id": null
}
curl -sS -X POST 'https://mcp.domesticmonero.com/mcp' \
-H 'Authorization: Bearer dm_YOUR_TOKEN_HERE' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {},
"clientInfo": { "name": "curl", "version": "0" }
}
}'

A valid Bearer format reaches the MCP session (SSE event: message with serverInfo.name = domesticmonero). Tool calls still require a live Profile token.

Verify​

After the client connects, call auth_whoami (no arguments).

Success: JSON for your Mini App profile (same account that published the token) — not an empty shell and not another user’s data.

If the tool is missing or auth fails: confirm the URL ends with /mcp, the header is Authorization: Bearer …, and the token was not revoked. More cases: MCP tools → Troubleshooting.

Stay safe​

  • Never paste DM_TOKEN into chat, group messages, or screenshots.
  • If a token leaks, Revoke it in Profile → MCP access, then publish a new one.
  • Use only https://mcp.domesticmonero.com/mcp and the official bot deep link.
  • Prefer client tool approval / allowlists when the host supports them — an agent can call every exposed tool.
  • For human help, message the official bot /support with Trade #ref when a trade is involved. See Cancel Trade, Cancel Offer, and /support.

Next​

Bot resmi: @domestic_monero_bot — Buka Mini App

Buka di Telegram