Agoralia docs
Connect

MCP

Connect an MCP client to Agoralia — endpoint, claude mcp add, the OAuth consent flow, available tools, and scopes.

MCP

Agoralia is an MCP server. Connect any MCP-capable client (Claude Desktop, Claude Code, or your own host) and drive the platform — agents, campaigns, calls, contacts, numbers, knowledge base, compliance — through tools.

  • Endpoint: https://api.agoralia.app/mcp
  • Transport: streamable HTTP
  • Auth: OAuth 2.1 with Dynamic Client Registration (DCR)

Add the server

claude mcp add --transport http agoralia https://api.agoralia.app/mcp

Other clients: point them at https://api.agoralia.app/mcp over HTTP transport.

On first connect the client runs the OAuth 2.1 authorization flow:

  1. The client registers itself dynamically (DCR) and opens the Agoralia authorization page.
  2. You sign in to your workspace and approve the consent screen — review the scopes the client is requesting before granting.
  3. Agoralia issues a Bearer access token (and refresh token). The client sends it as Authorization: Bearer … on every MCP call.

You can review and revoke granted clients in the dashboard at any time. Revoking invalidates the token immediately.

MCP operates on the gated agent surface. Risk-tiered actions (launching a campaign, placing live calls, purchasing a number) can return a guided "approval required" response; approve it in the dashboard, then retry. See Approvals & the gate.

Available tools

The server exposes the Agoralia surface as MCP tools, grouped by area:

  • Agentslist_agents, get_agent, create_agent, update_agent, delete_agent, publish_agent, unpublish_agent, test_agent, list_voices.
  • Campaignslist_campaigns, get_campaign, create_campaign, update_campaign, delete_campaign, launch_campaign, pause_campaign, resume_campaign, duplicate_campaign, get_campaign_leads, add_campaign_lead, get_cost_estimate, get_attestation_status, generate_attestation, sign_attestation.
  • Contacts & leadslist_contacts, get_contact, create_contact, create_contacts_bulk, delete_contact, search_contacts, add_to_dnc, check_dnc.
  • Calls & resultslist_calls, get_call, get_call_transcript, get_call_analysis, get_call_recording_url, search_calls.
  • Numberslist_numbers, get_number_credit, get_credit_transactions, search_available_numbers, purchase_number, topup_credit, link_number, list_available_countries, get_topup_packages.
  • Integrations (BYO carriers)connect_provider, list_provider_status, list_provider_numbers.
  • Messagingsend_message (SMS / WhatsApp), list_conversations, get_conversation_messages, get_messaging_usage.
  • Pipelineslist_pipelines, get_pipeline, create_pipeline, activate_pipeline, delete_pipeline, create_smart_pipeline.
  • Workflowslist_workflows, get_workflow, trigger_workflow.
  • Journeysget_journey, configure_journey.
  • Knowledge baselist_kb_sources, add_kb_text, add_kb_url, add_kb_qa, search_kb, delete_kb_source, get_playbook.
  • Complianceget_compliance_status, list_compliant_countries, check_dnc, check_number_dnc, add_to_dnc, remove_from_dnc, get_dnc_list.
  • Analytics & billingget_workspace_stats, get_daily_stats, get_cost_breakdown, get_billing_usage, get_billing_transactions, get_plans, export_report.
  • Workspaceget_workspace_info, list_team_members, list_integrations, get_workspace_settings.

Before launching campaigns or purchasing numbers, the model should show details and a cost estimate, then ask for explicit confirmation.

Scopes

The consent screen requests the scopes the client needs to operate. They map to the same permission model as the REST API — see the full table in Authentication → Scopes. The gate additionally enforces per-action RBAC by your role, regardless of the granted scopes.

Next