@runehand/mcp-server
@runehand/mcp-server
Servidor MCP que envuelve la API pública de Runehand v1 como herramientas, para que un cliente MCP (Claude Desktop, Claude Code, etc.) pueda operar bots de Runehand directamente: listar bots y flujos, leer y responder conversaciones, gestionar leads y consultar analíticas.
Puesta en marcha
Genera una clave de API en
https://app.runehand.co/settings/api-keys(requiere un plan Pro o Enterprise, y el rolowneroadminen el espacio de trabajo). La clave en texto plano se muestra una sola vez: cópiala.Añade esto a la configuración de tu cliente MCP (ejemplo:
claude_desktop_config.jsonde Claude Desktop):
{
"mcpServers": {
"runehand": {
"command": "npx",
"args": ["-y", "@runehand/mcp-server"],
"env": { "RUNEHAND_API_KEY": "rh_live_..." }
}
}
}Reinicia tu cliente MCP. Ahora debería listar 9 herramientas de Runehand.
Related MCP server: eduframe-mcp
Configuración
Variable de entorno | Requerida | Por defecto | Propósito |
| Sí | — | Token Bearer de |
| No |
| Solo para pruebas locales o de staging. |
Herramientas
Herramienta | Descripción |
| Lista los bots que pertenecen al espacio de trabajo propietario de la clave de API. |
| Lista los flujos que pertenecen a un bot, dado el UUID del bot. |
| Obtiene un flujo individual, incluidos sus nodos en formato ejecutable. |
| Lista conversaciones, opcionalmente filtradas por |
| Obtiene una conversación individual, incluidos sus mensajes. |
| Envía un mensaje como agente en una conversación existente. |
| Lista leads, opcionalmente filtrados por |
| Crea un lead directamente, sin una conversación asociada. |
| Obtiene KPIs del espacio de trabajo y estadísticas rápidas para un rango de fechas. |
Los errores de la API de Runehand se muestran como errores de herramienta con el formato "{code}: {message}" (p. ej. not_found: Not found.) — consulta la tabla de códigos de error en la documentación de la API.
Desarrollo
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/Licencia
MIT
Available Tools
9 toolscreate_leadCreate leadB
Create a lead directly, without an associated conversation. Does not trigger the LeadCaptured event.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| tags | No | ||
| No | |||
| notes | No | ||
| phone | No | ||
| bot_id | Yes | UUID of the bot this lead belongs to. | |
| source | No | Defaults to 'api' when omitted. | |
| custom_fields | No |
get_analyticsGet analytics dashboardA
Get workspace KPIs and quick stats for a date range, same data as the in-app dashboard.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Range end (YYYY-MM-DD). Defaults to today. | |
| from | No | Range start (YYYY-MM-DD). Defaults to 30 days before "to". |
get_conversationGet conversation detailA
Get a single conversation, including its messages in chronological order.
| Name | Required | Description | Default |
|---|---|---|---|
| conversation_id | Yes | UUID of the conversation to fetch. |
get_flowGet flow detailB
Get a single flow, including its nodes in executable format.
| Name | Required | Description | Default |
|---|---|---|---|
| flow_id | Yes | UUID of the flow to fetch. |
list_botsList botsB
List the bots that belong to the workspace that owns the API key.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| per_page | No |
list_conversationsList conversationsA
List conversations for the workspace, optionally filtered by bot_id and/or status.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| bot_id | No | Filter by bot UUID. | |
| status | No | ||
| per_page | No |
list_flowsList flowsC
List the flows that belong to a bot, given the bot's UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| bot_id | Yes | UUID of the bot whose flows to list. | |
| per_page | No |
list_leadsList leadsB
List leads for the workspace, optionally filtered by bot_id and/or status.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| bot_id | No | Filter by bot UUID. | |
| status | No | ||
| per_page | No |
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.
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | Message text, max 4096 characters. | |
| conversation_id | Yes | UUID of the conversation to send the message in. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
9 tool updates
v0.1.0- First observed
create_lead - First observed
get_analytics - First observed
get_conversation - First observed
get_flow - First observed
list_bots - First observed
list_conversations - First observed
list_flows - First observed
list_leads - First observed
send_message
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.142 npm8MIT