Connect your AI Agents to Podium in minutes
Available tools
list_campaigns
List all campaigns with optional status filtering. Returns campaigns sorted by updatedAt in descending order. Filter by status: ACTIVE, COMPLETED, DRAFT, ERROR, INACTIVE, IN_PROGRESS, SCHEDULED, STOPPED, SUSPENDED, ARCHIVED.
get_campaign
Get a campaign by UID. Returns detailed campaign information including name, message, status, locations, and timestamps. Use list_campaigns to find campaign UIDs.
create_campaign
Create a new automated campaign. Requires name, status (ACTIVE, DRAFT, etc.), and list of location UIDs. Optionally include message text and conversation settings. Use list_locations to find location UIDs.
update_campaign
Update an existing campaign. Supply only the fields to change. Use get_campaign to retrieve current settings first. Use list_campaigns to find campaign UIDs.
delete_campaign
Delete a campaign by UID. This action cannot be undone. Use get_campaign first to verify you have the correct campaign before deleting.
create_campaign_message
Send a message through a campaign to a specific subscriber. Requires campaign UID and channel identifier (email or phone number). Use get_campaign to verify campaign status before sending messages.
list_contacts
List contacts with cursor pagination. Use cursor from page_info for next page.
get_contact
Get a contact by email or phone number. Use list_contacts to find valid identifiers.
create_contact
Create a new contact with email and/or phone. Upserts if contact exists.
delete_contact
Delete a contact by email or phone number. Cannot be undone.
get_conversation_messages
Get messages from a conversation with cursor pagination.
update_conversation_assignees
Update assignees for a conversation. Use list_users to find valid user UIDs.
list_locations
List locations with cursor pagination and search. Supports filtering by search term, fields, and updated timestamp. Use cursor from page_info for next page.
get_location
Get a location by UID. Returns detailed location information including name, address, phone numbers, and timestamps. Use list_locations to find location UIDs.
send_message
Send an SMS or email message to a contact. Specify recipient and message type. Use list_locations to find valid location UIDs.
list_users
List users with cursor pagination. Use cursor from page_info for next page.
validate_credential
Validate Podium credentials. Verifies credentials during setup.
list_webhooks
List all webhooks configured for the account. Use cursor from page_info for next page.
get_webhook
Get a webhook by UID. Use list_webhooks to find valid UIDs.
create_webhook
Create a webhook for event notifications. Requires location_uid or organization_uid. Specify target URL and event types.
update_webhook
Update an existing webhook configuration.
delete_webhook
Delete a webhook by UID. Cannot be undone.
How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Podium MCP server
FAQs on using Merge's Podium MCP server
What is a Podium MCP?
It's an MCP server that lets your agents access data and functionality from Podium via tools. Your agents can invoke these tools to send a text message to a customer, look up a conversation thread, create or update a contact record, launch a messaging campaign, and more.
Podium doesn't offer an MCP server purpose built for Podium, but you can use one from a third-party platform, like Merge Agent Handler.
How can I use the Podium MCP server?
The use cases naturally depend on the agent you've built, but here are a few common ones:
- Missed-call text-back: when a call to a location goes unanswered, the agent finds or creates the caller as a contact and sends a text through Podium so the lead gets a response before they call a competitor
- Review request follow-up: after a job or appointment closes out in a scheduling or CRM tool, the agent creates the customer as a Podium contact and sends a review request message, timed to when the experience is still fresh
- Lead routing across locations: when a new conversation comes in, the agent reads the message thread and reassigns it to the right team member or location using conversation assignee updates, instead of leaving it in a shared queue
- Payment reminder nudge: the agent checks an external billing system for a past-due balance and sends a short text reminder through Podium, cutting down on emailed invoices that go unopened
What are popular tools for Podium's MCP server?
Here are some of the most commonly used tools:
send_message: sends an SMS or email message to a contact through Podium. Call this when an agent needs to reach a customer directly, like a missed-call text-back or a payment reminder
get_conversation_messages: retrieves the message history for a given conversation. Useful for agents that need context on prior exchanges before drafting a reply
create_contact: adds a new contact to Podium, or upserts if one already exists for that email or phone number. Good for workflows that sync leads or customers in from another system
get_contact: looks up an existing contact by email or phone. Helpful when an agent needs to confirm a customer already exists before sending a message
create_campaign: sets up a new automated messaging campaign. Use this when an agent needs to kick off a batch outreach, like a round of review requests
update_conversation_assignees: changes who's assigned to a conversation. Call this when an agent is routing an inbound thread to the right person or team
What makes Merge Agent Handler's Podium MCP server better than alternative Podium MCP servers?
There are several reasons to use Merge Agent Handler's Podium MCP server over building or using an alternative:
- Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Podium, this means you can prevent customer phone numbers and payment details from being exposed even when the agent has broad read access
- Managed authentication and credentials: Merge stores and refreshes Podium credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or manage token rotation manually
- Real-time observability and audit trail: Every tool call made against Podium is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent read or wrote without instrumenting anything yourself
- Tool Packs and controlled access: Tool Packs let you bundle specific Podium tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more
How can I start using Merge Agent Handler's Podium MCP server?
You can take the following steps:
1. Create or log into your Merge Agent Handler account.
2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.
3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.
4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Podium and complete the auth flow. Merge stores and manages the credentials going forward.
5. Open a Claude Code session and start querying Podium data directly. The first time you use a Podium tool, a Magic Link may appear to complete connector authentication.
If you want to connect Merge Agent Handler's Podium MCP with internal or customer-facing agentic products, you can follow the steps in our docs.
Can employees use Merge Agent Handler to connect their AI tools to Podium?
Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Podium without bypassing IT governance.
IT can provision access by role or group via SCIM. A front desk coordinator, for example, gets Podium access to send appointment reminders, Google Calendar access to check availability, and Slack access to flag urgent customer messages; while a marketing manager gets Podium access to launch review request campaigns, HubSpot access to sync contact records, and Google Sheets access to track campaign performance.
Every tool call an employee's AI makes to Podium is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
