Facebook
LinkedIn
YouTube
Getting Started
Authentication
Authentication
  • V2 Authentication (Deprecated)
  • V3 Authentication
V2 API Documentation (Deprecated)V3 API DocumentationDialer SDKMCP
Getting Started
Authentication
Authentication
  • V2 Authentication (Deprecated)
  • V3 Authentication
V2 API Documentation (Deprecated)V3 API DocumentationDialer SDKMCP
  1. MCP
  • Convirza MCP Server
  • Quickstart
  • Authentication & Access
  • Tools Reference
  • Example Prompts
  • Troubleshooting
  1. MCP

Convirza MCP Server

Use Convirza from inside your AI assistant. The Convirza MCP server lets Claude, ChatGPT, Cursor, VS Code, Codex and any other MCP-compatible client work with your Convirza account in plain language — pull call transcripts and scores, review campaigns, look up users and numbers, and manage your account, all by asking.
MCP (Model Context Protocol) is the open standard AI assistants use to connect to external tools. Convirza runs a first-party, hosted MCP server, so there is nothing to install or run yourself: you add one URL to your assistant and sign in with your Convirza account.

What you get#

Your data in conversation — calls, transcripts, Conversation Analytics® scores, campaigns, tracking numbers, users and groups, all queryable by asking.
Actions, not just answers — create and update campaigns, manage routing and geo-locations, add tags, and more, subject to your Convirza role.
Your permissions come with you — the server acts as you. Admins can manage, standard users can work, read-only users can read. Nothing your account can't do in Convirza becomes possible through the assistant.
One sign-in, then it just works — OAuth 2.0 with 7-day tokens and automatic refresh. Your password is never shared with the assistant.
Works everywhere MCP does — Claude (web, desktop, mobile, Claude Code), ChatGPT, Cursor, VS Code, Codex, and any client that supports remote MCP servers.

How it works#

Your AI assistant (Claude, ChatGPT, Cursor, …)
  └── connect.convirza.com/mcp   (Convirza MCP server, hosted)
        ├── OAuth 2.0 sign-in ── you authenticate on a Convirza page; the assistant receives a token
        └── Convirza Public API v3 ── every tool call runs as your user, with your role and permissions
When you first connect, your assistant opens a Convirza sign-in page. You enter your Convirza email and password there — on Convirza's page, not in the assistant. Convirza returns a scoped access token to the assistant, and from then on every request the assistant makes runs under your account with exactly your permissions.

Requirements#

RequirementDetail
Convirza accountAny active account. Role must be Admin, Standard or Read-Only (see Authentication & access)
MCP clientAny client supporting remote MCP servers over streamable HTTP — Claude, ChatGPT (developer mode), Cursor, VS Code, Codex, and others
NetworkYour client must be able to reach connect.convirza.com. If your organization filters outbound traffic, ask IT to allow that host

Server details#

Server URLhttps://connect.convirza.com/mcp
TransportStreamable HTTP (current MCP transport)
Legacy transporthttps://connect.convirza.com/sse — for older clients that only support SSE
AuthenticationOAuth 2.0 authorization code with PKCE; dynamic client registration supported
Tools112, across users, groups, calls, campaigns, numbers, routing, scoring, integrations and more
CostIncluded with every Convirza account at no extra charge

Next steps#

1.
Quickstart — connect your assistant in under a minute
2.
Authentication & access — how sign-in works, what each role can do, how to disconnect
3.
Tools reference — everything the server can do, grouped by area
4.
Example prompts — things to ask on day one
5.
Troubleshooting — common messages and what they mean
Modified at 2026-09-04 11:30:45
Next
Quickstart
Built with