Skip to main content
Glama
@runehand/mcp-server

@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

  1. Generieren Sie einen API-Schlüssel unter https://app.runehand.co/settings/api-keys (erfordert einen Pro- oder Enterprise-Plan und die Rolle owner oder admin im Workspace). Der Klartextschlüssel wird nur einmal angezeigt – kopieren Sie ihn.

  2. Fügen Sie dies zur Konfiguration Ihres MCP-Clients hinzu (Beispiel: claude_desktop_config.json von Claude Desktop):

{
  "mcpServers": {
    "runehand": {
      "command": "npx",
      "args": ["-y", "@runehand/mcp-server"],
      "env": { "RUNEHAND_API_KEY": "rh_live_..." }
    }
  }
}
  1. Starten Sie Ihren MCP-Client neu. Er sollte nun 9 Runehand-Tools auflisten.

Related MCP server: eduframe-mcp

Konfiguration

Umgebungsvariable

Erforderlich

Standard

Zweck

RUNEHAND_API_KEY

Ja

—

Bearer-Token von /settings/api-keys.

RUNEHAND_API_BASE_URL

Nein

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

Nur für lokale/Staging-Tests überschreiben.

Werkzeuge

Werkzeug

Beschreibung

list_bots

Listet die Bots des Workspace auf, dem der API-Schlüssel gehört.

list_flows

Listet die Flows auf, die zu einem Bot gehören, anhand der Bot-UUID.

get_flow

Ruft einen einzelnen Flow ab, einschließlich seiner Knoten im ausführbaren Format.

list_conversations

Listet Konversationen auf, optional gefiltert nach bot_id und/oder status.

get_conversation

Ruft eine einzelne Konversation ab, einschließlich ihrer Nachrichten.

send_message

Sendet eine Nachricht als Agent in einer bestehenden Konversation.

list_leads

Listet Leads auf, optional gefiltert nach bot_id und/oder status.

create_lead

Erstellt einen Lead direkt, ohne zugehörige Konversation.

get_analytics

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 tools
create_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

    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.

    Related MCP Connectors

    Related MCP Servers