Skip to main content
Glama
@runehand/mcp-server

@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

  1. Genera una clave de API en https://app.runehand.co/settings/api-keys (requiere un plan Pro o Enterprise, y el rol owner o admin en el espacio de trabajo). La clave en texto plano se muestra una sola vez: cópiala.

  2. Añade esto a la configuración de tu cliente MCP (ejemplo: claude_desktop_config.json de Claude Desktop):

{
  "mcpServers": {
    "runehand": {
      "command": "npx",
      "args": ["-y", "@runehand/mcp-server"],
      "env": { "RUNEHAND_API_KEY": "rh_live_..." }
    }
  }
}
  1. 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

RUNEHAND_API_KEY

Sí

—

Token Bearer de /settings/api-keys.

RUNEHAND_API_BASE_URL

No

https://app.runehand.co/api/v1

Solo para pruebas locales o de staging.

Herramientas

Herramienta

Descripción

list_bots

Lista los bots que pertenecen al espacio de trabajo propietario de la clave de API.

list_flows

Lista los flujos que pertenecen a un bot, dado el UUID del bot.

get_flow

Obtiene un flujo individual, incluidos sus nodos en formato ejecutable.

list_conversations

Lista conversaciones, opcionalmente filtradas por bot_id y/o status.

get_conversation

Obtiene una conversación individual, incluidos sus mensajes.

send_message

Envía un mensaje como agente en una conversación existente.

list_leads

Lista leads, opcionalmente filtrados por bot_id y/o status.

create_lead

Crea un lead directamente, sin una conversación asociada.

get_analytics

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 tools
create_leadCreate leadB

Create a lead directly, without an associated conversation. Does not trigger the LeadCaptured event.

NameRequiredDescriptionDefault
nameNo
tagsNo
emailNo
notesNo
phoneNo
bot_idYesUUID of the bot this lead belongs to.
sourceNoDefaults to 'api' when omitted.
custom_fieldsNo
get_analyticsGet analytics dashboardA

Get workspace KPIs and quick stats for a date range, same data as the in-app dashboard.

NameRequiredDescriptionDefault
toNoRange end (YYYY-MM-DD). Defaults to today.
fromNoRange start (YYYY-MM-DD). Defaults to 30 days before "to".
get_conversationGet conversation detailA

Get a single conversation, including its messages in chronological order.

NameRequiredDescriptionDefault
conversation_idYesUUID of the conversation to fetch.
get_flowGet flow detailB

Get a single flow, including its nodes in executable format.

NameRequiredDescriptionDefault
flow_idYesUUID of the flow to fetch.
list_botsList botsB

List the bots that belong to the workspace that owns the API key.

NameRequiredDescriptionDefault
pageNo
per_pageNo
list_conversationsList conversationsA

List conversations for the workspace, optionally filtered by bot_id and/or status.

NameRequiredDescriptionDefault
pageNo
bot_idNoFilter by bot UUID.
statusNo
per_pageNo
list_flowsList flowsC

List the flows that belong to a bot, given the bot's UUID.

NameRequiredDescriptionDefault
pageNo
bot_idYesUUID of the bot whose flows to list.
per_pageNo
list_leadsList leadsB

List leads for the workspace, optionally filtered by bot_id and/or status.

NameRequiredDescriptionDefault
pageNo
bot_idNoFilter by bot UUID.
statusNo
per_pageNo
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.

NameRequiredDescriptionDefault
contentYesMessage text, max 4096 characters.
conversation_idYesUUID of the conversation to send the message in.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 9 tool updatesv0.1.0
    • First observedcreate_lead
    • First observedget_analytics
    • First observedget_conversation
    • First observedget_flow
    • First observedlist_bots
    • First observedlist_conversations
    • First observedlist_flows
    • First observedlist_leads
    • First observedsend_message

TDQS

A3.6/5.0

Scored across 9 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo recent community issues

Related MCP Connectors

Related MCP Servers