RegalMCP

Endpoint

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tools

• get-brand — Fetch your brand's configuration, including telephony, compliance, and queue settings.
• query-regal-kb — Query the Regal knowledge base with a natural language question.
• list-regal-skills — List available skills.
• list-ai-agents — List AI agents configured for your brand, with pagination and channel-type filtering.
• fetch-agent — Fetch an active version of a specific agent variant, including its full configuration and prompt.
• fetch-latest-agent — Fetch highest version (active, draft or deactivated) of a specific agent variant; use before edit-agent for updates.version.
• fetch-agent-version — Fetch a specific version of an agent variant (including historical ones).
• list-ai-agent-variants — List all variants for a given agent, including traffic allocation.
• list-ai-agent-versions — List all versions for a given agent variant.
• fetch-test-cases — Fetch test cases associated with an agent.
• explore-agent-context — Returns workflow instructions for building and understanding AI agent configurations.
• summarize-agent-plan — Returns a plan template to guide agent design decisions.
• generate-agent-config — Returns section-by-section guidance for editing an agent config.
• get-prompting-best-practices — Returns Regal's static prompting reference for agent builders.
• get-ai-agent-tool-context — Returns the tool-context reference used when building agent tool configurations.
• fetch-simulation-transcript — Fetch the transcript from a completed simulation run.
• list-recordings — List call recordings, with filters for date range, agent, disposition, and phone number.
• fetch-recording-transcripts — Fetch transcripts for one or more recordings (up to 5 SIDs per call).
• get-trackers-lookup — Return the list of tracker IDs and names defined for your brand.
• list-dispositions — Lists dispositions in the account.
• list-analysis-data-points — List analysis data point definitions used for call scoring and QA.
• list-journeys — List journeys with search and pagination support.
• fetch-journey — Fetch a full journey definition, including its flow and node configuration. Webhook auth headers are redacted.
• list-journey-versions — List all saved versions of a journey.
• fetch-journey-version — Fetch a specific historical version of a journey for diffing or review.
• list-profile-journey-executions — List journey executions for a given contact profile.
• get-profile-journey-execution-nodes — Get the node-level detail of a specific journey execution.
• lookup-profile — Look up a contact profile by phone, email, name, or external ID. Returns multiple candidates if the query is ambiguous.
• fetch-profile — Fetch a full contact profile by profile ID.
• fetch-profile-events — Fetch event history for a contact profile, with type and cursor-based pagination.
• list-profile-versions — List all saved versions of a contact profile.
• fetch-profile-version — Fetch a specific historical snapshot of a profile.
• list-users — List agent and user accounts in your brand.
• fetch-user — Fetch a specific user account by email, including queue assignments.
• list-queues — List routing queues and their eligibility rules.
• list-tasks — List tasks by state, queue, type, or phone number, with pagination.
• fetch-task — Fetch a specific task by SID.
• get-task-events — Fetch routing event history for a task.
• get-routing-rules — Get routing rule definitions for your brand.
• get-routing-rule-versions — Get version history for a named routing rule.
• get-simulation-progress — Poll the progress of a running simulation.
• list-business-profiles — List your business profile(s).
• list-active-phone-numbers — Lists your Regal provisioned phone numbers.
• list-brandedphone-numbers — Lists your phone numbers that were uploaded for branded caller id and/or spam remediation.
• create-agent — Create a new AI agent.
• edit-agent — Edit an existing agent (saves as a draft version).
• create-ai-agent-variant — Create a new variant for an existing agent.
• set-variant-traffic-allocations — Set traffic allocation percentages across all variants of an agent.
• create-test-cases — Create test cases for an agent.
• edit-test-case — Edit an existing test case.
• delete-test-cases — Delete one or more test cases.
• start-simulation-run — Start a simulation run against an agent and a set of test cases.
• create-dispositions — Creates dispositions.
• edit-dispositions — Updates existing dispositions.
• create-analysis-data-point — Creates a new custom AI analysis data point.
• edit-analysis-data-points — Edit one or more existing custom AI analysis data points.
• delete-analysis-data-points — Delete one or more existing custom AI analysis data points.
• create-branded-phone-number — Adds a phone number for branded caller id and/or spam remediation.
• update-branded-phone-number — Updates a phone number for branded caller id and/or spam remediation, including registering/unregistering numbers for carriers.
• delete-branded-phone-number — Deletes a phone number from branded caller id and/or spam remediation.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.