Skip to content

MCP Server ​

The Genudo Console exposes a Model Context Protocol (MCP) server. MCP is an open standard that lets AI clients (Claude, ChatGPT, Codex, Gemini CLI, Cursor, Windsurf, and any MCP-compatible agent) discover and invoke tools at runtime over a persistent connection.

Your token can invoke tools that manage pipelines, stages, actions, variables, opportunities, contacts, messages, and analytics — all as the authenticated user, respecting the same permission rules as the REST API.

Endpoints ​

EndpointPurpose
POST /mcpJSON-RPC 2.0 — all MCP requests (initialize, tools/list, tools/call)
DELETE /mcpTerminate a session

The transport is Streamable HTTP (MCP spec 2025-03-26): every request is a stateless POST with a JSON-RPC 2.0 body, every response is application/json. The MCP handshake, tool discovery, and per-tool invocations all flow through your client library — you rarely call these endpoints by hand. See Connect.

Authentication ​

Two ways in, both landing on the same mcp:use scope:

  • OAuth (default) — your client hits the endpoint, gets a 401 with discovery headers, registers itself, and opens a browser sign-in. Approve access and you're connected. No token to create or paste. This is what every path on Connect a client uses.
  • Bearer token — send Authorization: Bearer <token> for custom agents and SDKs that don't do OAuth discovery. Tokens are created from the Authentication guide and can be scoped, revoked, and expired independently per integration.

Tools inherit whatever scopes your token carries. A token with mcp:use + opportunities:read can call tools that read opportunities but not those that write. A token with only mcp:use can call tools that require no additional scope.

See Authentication for token creation and scope definitions.

Available tools ​

32 tools across 5 groups.

Analytics ​

Account health, messaging volume, AI performance & cost.

ToolDescription
get_account_summaryAccount snapshot: total pipelines, opportunities, and message counts
get_messaging_statsMessaging volume filtered by date range, pipeline, or channel provider
get_ai_performanceTotal AI messages, average response time, and total cost

Discover ​

Pull and filter your workspace data — the starting point for everything.

ToolDescription
list_pipelinesYour pipelines with status, description, and stage counts
list_pipeline_stagesStages of a pipeline in stage order
list_actionsActions for a pipeline, optionally filtered to a specific stage
list_action_resultsExecution log for a pipeline's actions — did the webhook fire, and what came back
list_variablesPipeline variables available for use in actions
list_contactsContacts with filters for status, priority, tags, and search
list_opportunitiesOpportunities with contact, stage, and tags context
list_messagesMessages across pipelines, cursor-paginated
list_knowledge_tablesKnowledge tables with column counts and the pipelines they are attached to
search_knowledge_tableSearch a knowledge table by natural-language query
list_knowledge_pointsRows in a knowledge table with their default_ids, paginated
list_model_poolCurrent Smart Routing tier assignments for a pipeline
get_stage_followupFollowup configuration and interval schedule for a stage
get_pipeline_optionsValid agent types, AI providers, models, languages, dialects, and channels

Build ​

Create pipelines, stages, variables, webhook actions, followups, and knowledge tables.

ToolDescription
start_pipeline_journeyGuided builder — the intended first call for a new pipeline
create_pipelineNew pipeline with agent type, AI model, language, persona, and instructions
create_stageAdd a neutral, won, or lost stage with its own AI behavior
create_variableDefine fixed, system, action, or AI-extracted variables
create_actionOutbound HTTP webhook action for a pipeline or stage
create_followupRe-engagement sequence for a stage with timed intervals
create_knowledge_tableStructured knowledge base table with columns
upsert_knowledge_pointsInsert or update rows in a knowledge table

Update ​

Tune live pipelines, stages, actions, deals, followups, and Smart Routing.

ToolDescription
update_pipelineChange settings, persona, AI model, limits, and which knowledge tables the agent can search
update_model_poolSet the four Smart Routing tiers on an existing pipeline
update_stageEdit instructions, entry conditions, order, or opening messages
update_actionTune an existing action's request or trigger
update_variableEdit a variable's value or metadata
update_opportunitiesBulk update status, stage, tags, or notes
update_followupChange followup intervals, instructions, or activation status

Delete ​

ToolDescription
delete_knowledge_pointsRemove specific rows from a knowledge table by their default_id values

For full parameter reference see Tools. The plugin adds skills and agents on top of these tools — see Skills & agents.

When to use MCP vs the REST API ​

  • REST: one-shot integrations, webhooks, cron jobs, server-to-server automation.
  • MCP: interactive AI clients that discover capabilities at runtime and stream results back to a chat interface.

You can use both from the same PAT.