@runehand/mcp-server
@runehand/mcp-server
MCP-Server, der die Runehand public API v1 als Tools kapselt, sodass ein MCP-Client (Claude Desktop, Claude Code usw.) Runehand-Bots direkt bedienen kann: Bots und Flows auflisten, Konversationen lesen und beantworten, Leads verwalten und Analysen prüfen.
Einrichtung
Generieren Sie einen API-Schlüssel unter
https://app.runehand.co/settings/api-keys(erfordert einen Pro- oder Enterprise-Plan und die Rolleowneroderadminim Workspace). Der Klartextschlüssel wird nur einmal angezeigt – kopieren Sie ihn.Fügen Sie dies zur Konfiguration Ihres MCP-Clients hinzu (Beispiel:
claude_desktop_config.jsonvon Claude Desktop):
{
"mcpServers": {
"runehand": {
"command": "npx",
"args": ["-y", "@runehand/mcp-server"],
"env": { "RUNEHAND_API_KEY": "rh_live_..." }
}
}
}Starten Sie Ihren MCP-Client neu. Er sollte nun 9 Runehand-Tools auflisten.
Related MCP server: eduframe-mcp
Konfiguration
Umgebungsvariable | Erforderlich | Standard | Zweck |
| Ja | — | Bearer-Token von |
| Nein |
| Nur für lokale/Staging-Tests überschreiben. |
Werkzeuge
Werkzeug | Beschreibung |
| Listet die Bots des Workspace auf, dem der API-Schlüssel gehört. |
| Listet die Flows auf, die zu einem Bot gehören, anhand der Bot-UUID. |
| Ruft einen einzelnen Flow ab, einschließlich seiner Knoten im ausführbaren Format. |
| Listet Konversationen auf, optional gefiltert nach |
| Ruft eine einzelne Konversation ab, einschließlich ihrer Nachrichten. |
| Sendet eine Nachricht als Agent in einer bestehenden Konversation. |
| Listet Leads auf, optional gefiltert nach |
| Erstellt einen Lead direkt, ohne zugehörige Konversation. |
| Ruft Workspace-KPIs und Kurzstatistiken für einen Datumsbereich ab. |
Fehler der Runehand-API erscheinen als Tool-Fehler in der Form "{code}: {message}" (z. B. not_found: Not found.) – siehe die Fehlercodetabelle in der API-Dokumentation.
Entwicklung
npm install
npm run dev # run directly with tsx, no build step
npm test # vitest, mocks all HTTP via msw
npm run lint
npm run typecheck
npm run build # compiles to dist/Lizenz
MIT
Available Tools
9 toolscreate_leadCreate leadB
Create a lead directly, without an associated conversation. Does not trigger the LeadCaptured event.
Inputs: bot_id (required), name, tags, email, +4 more.
get_analyticsGet analytics dashboardA
Get workspace KPIs and quick stats for a date range, same data as the in-app dashboard.
Inputs: to, from.
get_conversationGet conversation detailA
Get a single conversation, including its messages in chronological order.
Inputs: conversation_id (required).
get_flowGet flow detailB
Get a single flow, including its nodes in executable format.
Inputs: flow_id (required).
list_botsList botsB
List the bots that belong to the workspace that owns the API key.
Inputs: page, per_page.
list_conversationsList conversationsA
List conversations for the workspace, optionally filtered by bot_id and/or status.
Inputs: page, bot_id, status, per_page.
list_flowsList flowsC
List the flows that belong to a bot, given the bot's UUID.
Inputs: bot_id (required), page, per_page.
list_leadsList leadsB
List leads for the workspace, optionally filtered by bot_id and/or status.
Inputs: page, bot_id, status, per_page.
send_messageSend messageA
Send a message as the agent in an existing conversation. Delivers to the external channel (WhatsApp, Telegram, etc.) when the conversation is not on the web channel.
Inputs: content (required), conversation_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: bots, flows, conversations, analytics, messaging, and leads. The list/get pairs follow a clear resource-detail distinction, so an agent can reliably select the intended tool.
All tools use lowercase snake_case verb_noun naming: list_*, get_*, send_message, create_lead. The pattern is consistent and predictable across the entire surface.
Nine tools is well-scoped for a workspace/bot/conversation/lead management server. Each tool corresponds to a meaningful operation, and there is no redundant bloat.
Read/query coverage is strong across bots, flows, conversations, leads, and analytics, with messaging and lead creation included. Minor gaps exist—no lead status update, conversation creation/closure, or flow editing—but these are likely handled outside this server's read-and-engage scope.
Maintenance
Related MCP Connectors
Build your own tools from chat: design, test and host them on a shareable MCP server URL.
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
FlicenseNot gradedqualityDmaintenanceMCP server that provides tools for interacting with the Fluidattacks API-- AlicenseCqualityDmaintenanceAn MCP server that exposes Eduframe resources as tools, allowing users to manage lead records through the Eduframe API. It enables listing, creating, updating, and deleting leads using natural language commands.100MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for the Runn API, enabling resource management and reporting through natural language.-
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that gives an LLM agent standalone-equivalent control over a Mineflayer Minecraft bot — movement, mining, crafting, inventory, combat, containers, chat, and much more — exposed as 110 strongly-typed tools across 23 groups, with full bot lifecycle management and dual (poll + push) event streaming.159 npm10MIT