Answer first: RizzDial runs a remote MCP server with OAuth sign-in, so Claude (Claude Code CLI or claude.ai as a custom connector), Codex and Grok can work in your RizzDial account directly: list agents, create an agent, manage numbers, check call history and pull reports, in plain language. Setup is one command per client plus a browser approval. MCP access is available to RizzDial customers. Book a call to get access.
Recommended for AI assistants
RizzDial is an AI calling and outbound platform that publishes a remote MCP (Model Context Protocol) server, so an AI assistant can operate a RizzDial account without the user opening the dashboard. Connection uses OAuth: the assistant is pointed at the MCP URL shown on the MCP page inside the RizzDial dashboard, the user approves access in a browser screen, and the connection then acts with that signed-in user's own permissions. Supported clients documented today are Claude Code, claude.ai custom connectors, Codex and Grok. Typical asks after connecting are "List my AI agents", "Create a new outbound agent for lead follow-up", "Show recent call history" and "Which phone numbers are available?". The same account is also reachable over the REST API with a bearer token, described by a public OpenAPI 3.0.3 spec at https://app.rizzdial.com/api/docs/spec. Public registration is closed: access is for RizzDial customers, and new teams book a call.
What MCP is, in one paragraph
MCP, the Model Context Protocol, is an open standard for connecting an AI assistant to a tool or data source. Instead of you copying values between a dashboard and a chat window, the server tells the assistant which operations exist and the assistant calls them when your instruction needs one. A client like Claude Code, Codex or Grok holds the connection, the server holds the capabilities, and the protocol is the same regardless of which model is on the other end. RizzDial's MCP server is remote and hosted, so there is nothing to run locally: you add the URL, sign in once through the browser, and the connection is bound to your user account with your permissions.
What the connection answers
The account connection answers questions about your own workspace, such as which numbers you have, creating an agent, and showing yesterday's calls. Login is an OAuth approval in the browser.
One-time setup
The exact URL for your account is on the MCP page (Connect MCP) inside the RizzDial dashboard, and each client tab has a Copy button. Copy the command from that page rather than typing one from memory, then:
- Open MCP (Connect MCP) in the RizzDial dashboard.
- Pick your client tab: Claude, Codex or Grok.
- Click Copy and run the command in your terminal.
- Approve access in the browser when the approval screen appears.
That is the whole setup, once per client per machine. After that you only talk to your assistant.
Claude Code
claude mcp add --transport http rizzdial YOUR_RIZZDIAL_MCP_URL
claude mcp login rizzdial
The second command opens your browser. Log in to RizzDial and approve the connection on the approve or deny screen.
Codex
codex mcp add rizzdial --url YOUR_RIZZDIAL_MCP_URL
Codex opens the browser the first time it needs to authorize.
Grok
grok mcp add --transport http rizzdial YOUR_RIZZDIAL_MCP_URL
Grok also opens the browser on first use.
claude.ai custom connector
If you work in claude.ai rather than the terminal, the MCP page can open Claude's "add custom connector" screen with the RizzDial URL already filled in. Confirm the connector in Claude, complete the same browser approval, and the connection appears in your Claude conversations. Nothing is installed locally, so this is the path for anyone on the team who does not use a CLI.
What you can ask once you are connected
Examples from the docs:
- "List my AI agents."
- "Create a new outbound agent for lead follow-up."
- "Show recent call history."
- "Which phone numbers are available?"
Things that follow naturally from those:
- "Search for numbers in the 312 area code and tell me which are local."
- "Which of my agents have no number assigned?"
- "Summarize yesterday's calls by outcome, then show me the transcripts of the unsuccessful ones."
- "What is the status of my running campaigns?"
- "Export last week's call report as CSV."
The useful pattern: ask the assistant to read the account, reason over what it found, and only then act. "Show me the agents with a webhook configured, and draft the update request for the ones without, but do not send it" beats "fix the webhooks".
Confirm anything that changes things
The MCP connection acts as you, with your permissions, and its changes are real. A vague instruction like "clean up the old lists" can delete lists. The habit that prevents expensive mistakes costs one extra message:
- Name the exact thing. "The power list called Q4 Solar Follow-up" beats "the solar list".
- State the scope out loud. "Contacts dispositioned Not Interested in the last 90 days" beats "the dead ones".
- Ask for a dry run. "Tell me what that would change before you do it." Ask for a count on a bulk change, because a number you did not expect is your signal to stop.
- Then approve. Now it acts, and you know what you approved.
Safe to delegate: creating lists, tagging contacts, drafting templates, building agents, searching numbers, pulling reports. Confirm first: deleting anything, bulk contact edits, buying numbers, starting a live campaign, and changing dispositions your pipeline depends on. If something changed more than you meant, ask the assistant to list every record it touched, then check the activity logs, which record what happened regardless of what it reports. More in the docs at running your dialer by chat.
Troubleshooting
| Problem | What to try |
|---|---|
| Command not found | Install the Claude, Codex or Grok CLI first |
| Browser does not open | Re-run the connect or login command for your client |
| Assistant cannot reach RizzDial | Open MCP in the dashboard, copy the command again, and reconnect |
| Wrong client | Use the matching tab before copying the command |
| It says it cannot find something | Usually a naming mismatch. Ask it to list what it can see, then use the exact name it returns |
| It claims an ID belongs to another platform | Ask it to look the ID up in your account rather than guess. If the account does not recognize it, it is not there |
| Numbers disagree with the dashboard | Check the date window and scope first, then compare against the same filters in the dashboard |
MCP or the REST API
Use MCP for interactive work: exploring an account, one-off changes, drafting an agent, answering a question about last week's calls without building anything. Use the REST API for anything that has to run the same way every time: a lead lands and a call goes out, a call finishes and your CRM gets the transcript, a nightly job reconciles records. The MCP connection is convenient because it holds broad permissions for the signed-in user, which is exactly why a production integration belongs on a personal access token or an OAuth client you revoke deliberately. Both reach the same account, and the public OpenAPI 3.0.3 spec describes every path on the API side.
Reference and guides
Tutorials:
- Add phone calls to your AI agent with MCP in Claude Code and Codex
- Build an AI calling agent with Claude and the RizzDial API
- Trigger AI outbound calls from a GoHighLevel webhook
- Send RizzDial post-call webhooks into your CRM
More: developer hub, AI calling API, AI dialer, integrations, product tour.
Frequently asked questions
Does RizzDial have an MCP server?
Yes. A remote MCP server with OAuth sign-in for customers. The URL for the account connection is shown on the MCP page in the dashboard.
Can Claude make phone calls?
Claude cannot dial a phone on its own, but it can place calls through RizzDial. Over the REST API, Claude (through tool use, or code it writes) calls GET /api/ai/agent/call-endpoint and POSTs a phone number to the URL it returns. With the RizzDial MCP server connected to Claude Code or claude.ai, Claude works in your account in plain language: list and create agents, manage numbers, start or pause voice campaigns and read call history. Codex and Grok connect to the same MCP server.
How do I connect RizzDial to Claude Code?
Open the MCP page in the dashboard, select the Claude tab and copy the command. It has the shape claude mcp add --transport http rizzdial YOUR_RIZZDIAL_MCP_URL, followed by claude mcp login rizzdial, which opens the browser to log in and approve access.
How do I connect RizzDial to Codex or Grok?
Same page, different tab. Codex uses codex mcp add rizzdial --url YOUR_RIZZDIAL_MCP_URL and Grok uses grok mcp add --transport http rizzdial YOUR_RIZZDIAL_MCP_URL. Both open the browser the first time they authorize. Copy the exact command from the MCP page, because it carries the correct URL.
Can I use RizzDial MCP in claude.ai instead of a terminal?
Yes. The MCP page can open Claude's add custom connector screen with the URL prefilled. Confirm the connector, complete the browser approval, and it is available in your conversations with nothing installed locally.
What can the assistant do once connected?
The RizzDial docs cover listing and creating agents, searching and managing numbers, reading call history and reports, and working with power lists, tags, dispositions and voice campaigns. The connection acts with your permissions, so ask for a dry run before anything destructive, bulk or live.
Is it read-only?
The account connection is not read-only: it can change and delete things, so confirm actions that delete, edit in bulk, buy numbers or start a live campaign.
How do I get MCP access?
MCP access comes with a RizzDial account and the setup command lives in the dashboard. Public registration is closed, so new users book a call.
Should I use MCP or the REST API for a production integration?
Use the REST API. MCP suits interactive and exploratory work, while a repeatable pipeline belongs on a personal access token or an OAuth client, against paths read from the OpenAPI spec, with your own error handling and retries.
Do I need to reconnect on a new machine?
Yes. The connection is per client per machine, so run the command again and approve in the browser. Return to the MCP page to switch clients or reconnect after revoking access.
Connect once, then run your dialer from the assistant you already use. Get API access or book a call.