Podium MCP Server
Inbox, reviews, review invites, contacts and payment requests for Podium.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/podium'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Podium API and MCP server: Let your AI agent clear the Podium Inbox and reviews.
Podium has no MCP server (checked 27 Oct 2026). Its REST API reaches almost everything on this page: conversations, assignees, review replies, invite links, contact tags and invoices. You get it only after Podium approves a developer account and your OAuth app, and then someone writes the code. Cotlet runs 14 Podium tools hosted, over MCP for agents and REST for scripts, in your own Podium login.
Inbox, reviews, review invites, contacts and payment requests for Podium. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Podium
- Page: https://cotlet.dev/integrations/podium-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Podium. Podium is a trademark of its owner. If Podium's own integrations cover what you need, use them first.
What can you automate in Podium?
- Answer new Google and Facebook reviews
- Assign Inbox chats by topic
- Send review invites for a visit list
- Reply to a text or email thread
- Request payment and chase open ones
- Tag contacts for the next bulk send
Does Podium have an MCP server or an API?
- Developer accounts take "a few days" to review, apps "generally ... within 2 weeks", and Podium "may deny you access to the Podium API for any reason".
- Nothing official reads your Bulk Messages credits; your plan has 250 (Core) or 500 (Pro) a month.
- Zapier has 6 triggers plus invoice and data feed actions. None replies to a review, assigns a chat or tags a contact.
| What you need | Podium API (approved app) | Zapier | Cotlet |
|---|---|---|---|
| Read the Inbox and a thread | Yes | No | Yes |
| Assign a conversation | Yes | No | Yes |
| Reply to a Google review | Yes | No | Yes, after your OK |
| Send a review invite | A link, then a message | Trigger only | Yes, after your OK |
| Request a payment | Yes | Create an Invoice | Yes, after your OK |
| What you need first | Developer account, app review, code | A Zapier plan | Your Podium login |
Checked 27 Oct 2026. Sources: Podium API: Getting started, Podium API reference, Podium OAuth scopes, Podium partner and API terms, Podium on Zapier, Podium pricing
How does Cotlet connect to Podium?
- Sign in to Podium. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Podium password, and no message, review reply, invite or payment request reaches a customer before you approve it.
Connect Podium to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to Podium in a Cloud Browser. Create a Cotlet account, open Podium in its Cloud Browser, sign in with your own Podium user (Core, Pro or Signature) and press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 into your agent's MCP server or connector settings.
- Allow the connection. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console instead.
https://cotlet.dev/mcp/v1 serves every app you enable on Cotlet, Podium included. Enable Podium after connecting and the agent needs a connector refresh before it lists the Podium tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: podium_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: podium_write
How to use the Podium REST API
Create your Cotlet API key
Create a Cotlet API key with access to Podium and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Podium in Cotlet and enable it for agents. Account access: Your own Podium login (what your agent can do follows your role and the features your plan includes).
Make your first Podium API request
REST:
curl https://cotlet.dev/api/v1/podium/locations \
-H "Authorization: Bearer $COTLET_API_KEY"
Read locations and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "podium",
"tool": "list_locations",
"result": {
"locations": [
{
"location_id": "loc_2b81",
"name": "Riverside Dental",
"city": "Salt Lake City"
},
{
"location_id": "loc_7c40",
"name": "Riverside Dental Orthodontics",
"city": "Provo"
}
]
}
}
Returns each location of your Podium account with its location_id and name. Use location_id as the location parameter of the other tools.
A single-location account returns one row. What you can open follows your own Podium role.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Podium workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Reviews from your connected review sites, with rating, text and whether you replied. Use list_reviews in your configured business report. |
| Make | HTTP > Make a request | One conversation with its messages, channel and assignee. Use get_conversation in your configured business report. |
| Python or Node.js | REST API | Payment requests with amount and status: pending, paid, refunded or canceled. Use list_payment_requests in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Podium; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Podium API endpoints and MCP tools
Inbox and conversations
A thread answers on its own channel: text, email, Facebook, Google or Instagram. Assigning reaches no customer, so it runs at once.
- List locations (
list_locations, read): Podium locations your login can open, with the ID the other tools take. - List conversations (
list_conversations, read): Inbox conversations with channel, contact, last message and assignee. - Get conversation (
get_conversation, read): One conversation with its messages, channel and assignee. - Send message (
send_message, write, asks first): Send a text or email from Podium, in an existing conversation or to a phone number or email. - Assign conversation (
assign_conversation, write): Assign a conversation to one or more teammates.
Reviews and review invites
Replies post only on Google and Facebook profiles connected to Podium. One invite per contact in 60 days.
- List reviews (
list_reviews, read): Reviews from your connected review sites, with rating, text and whether you replied. - Reply to review (
reply_to_review, write, asks first): Post a public reply to a Google or Facebook review. - Send review invite (
send_review_invite, write, asks first): Send a customer a review invitation with a review link, from a message template.
Contacts and bulk sends
Tags feed the audiences of your Bulk Messages; the send itself stays in Podium.
- List contacts (
list_contacts, read): Contacts from the Podium Contacts page, searchable by name, phone or email. - Get contact (
get_contact, read): One contact with phone, email, status, tags and custom fields. - Update contact tags (
update_contact_tags, write): Add or remove tags on a contact. - Get bulk message usage (
get_bulk_message_usage, read): How many bulk messages your plan allows and how many you used.
Payments
A request texts or emails a card payment link. Refunds and canceling stay on the Payments page.
- List payment requests (
list_payment_requests, read): Payment requests with amount and status: pending, paid, refunded or canceled. - Request payment (
request_payment, write, asks first): Send a customer a payment request with a link to pay by card.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/podium-api-mcp-server#tools
Who can see my Podium session, and how do I revoke it?
- What we store. Your signed-in Podium profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 14 Podium tools. No cookie and no login.
- What the session sees. The locations and pages your Podium user can open. No Payments access, no payment tools that work.
- What no tool touches. Refunds, Phones, Campaigns, Automations, bulk sends and billing.
- If Podium signs you out. We email you a sign-in link. You sign in yourself, we never do.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads what is open. Google reviews with no reply, and whether Podium can post on each one.
- Drafts by stars. Thanks by first name for 4 and 5 stars, a calm reply with your phone number for 1 to 3.
- Waits for your OK. Each reply waits in your Cotlet console. Legal claims, refunds and health details are held, not drafted.
- Reports back. Posted, held for you, and reviews on sites Podium cannot answer on.
| Action | Undo |
|---|---|
| Send a message | None; the text or email is delivered |
| Reply to a review | Edit or delete it in your Google or Facebook profile; it was public until then |
| Send a review invite | None, and it uses that contact's invite for 60 days |
| Request a payment | Cancel it on the Payments page; the link stops taking payment |
| Assign a conversation | Assign it again; nobody outside saw it |
| Update contact tags | Remove the tag; check automations that ran on it |
4 of the 6 write tools ask first. assign_conversation and update_contact_tags run at once, because an assignee or a tag reaches no customer. Reads run at once. For a scheduled run you can switch the wait off per tool.
Before posting, the agent reads the review list again, so a review a teammate or Podium's own AI answered in the meantime gets no second reply.
MCP call:
{
"name": "send_review_invite",
"arguments": {
"location": "loc_2b81",
"to": "+15555550142",
"template": "Review Invitation - Default"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/podium/review-invites \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"location":"loc_2b81","to":"+15555550142","template":"Review Invitation - Default"}'
Response:
{
"invite_id": "inv_52e8",
"to": "+15555550142",
"template": "Review Invitation - Default",
"status": "sent"
}
A practice management export or a nightly script can call the same tools over REST at /api/v1/podium, with one key and one price. A call your Podium user may not make returns an error and costs nothing. Every tool row above lists its REST path.
How much does the Podium MCP server cost?
About $43 a month for one dental office, 7,390 credits. On top of Podium itself: Core is $399 a month per location, Pro $599.
| Job | Calls | Credits |
|---|---|---|
| Reply to new Google reviews, daily | 2 × 30 | 600 |
| Assign the unassigned Inbox, each workday | 12 × 22 | 2,640 |
| Review invites for the week's 20 visits | 40 × 4 | 1,600 |
| Payment requests for finished treatment, weekly | 6 × 4 | 240 |
| Tag a 40-patient recall list, monthly | 81 × 1 | 810 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 7,390 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No developer account, app review or Pro upgrade
The month is our example: one location on Core, about 30 new reviews, a few unassigned chats each of 22 workdays, 20 finished visits a week and one recall list of 40 patients. Podium publishes no typical size. Dollars at the $29 pack rate.
Podium MCP server on GitHub, Merge or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Merge Agent Handler | A hosted Podium MCP server on the official API: conversations, messages, assignees, contacts, tags, campaigns. | Built for teams wiring agents into products. Free up to 2,000 calls a month, then $1,000 a month; review replies and invoices are not on its public tool list. |
| podium/podium_ex | Podium's own Elixir library for the API. 7 stars, last push 22 Mar 2024. | Needs an approved OAuth app; no MCP. |
| AI Reputation Specialist and AI Concierge | Podium's built-in AI answers reviews and leads inside Podium. | Pro at $599 a month per location; your own agent cannot hand it work. |
If you have developers and time for Podium's review, the API covers most of these jobs. If you want Podium's own AI on reviews, that is the Pro plan. If your agent should read reviews and chats, route the Inbox and send invites from your login today, Cotlet does that hosted.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Podium tools go to contact@cotlet.dev.
Podium API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Podium under Integrations in the console and sign in to Podium in its Cloud Browser. The trial begins when you sign up and needs no card.
How do I connect Podium to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Podium once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Podium account through Cotlet, in their phone apps too.
What can ChatGPT do in Podium?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Podium: reply to Google reviews; assign Inbox conversations to the right teammate; send review invites from a customer list. You ask in plain words, and anything that reaches other people waits for your OK first.
Which review sites can my agent reply on?
Google and Facebook, when those profiles are connected to Podium. Podium replies directly only on those two. For other sites it can send review invitations but not answer reviews, and Yelp and Trustpilot do not allow third-party integrations. list_reviews marks each review with can_reply.
Is there a limit on review invites?
Podium limits review invitation links for the same contact to one in 60 days. A second send_review_invite inside that window fails, and your agent skips the contact and lists it for you.
Does Podium have webhooks?
Yes, for approved API apps: message, contact and review events go to a URL you register, and for messages Podium sets the URL up for you. Cotlet sends no webhooks; to react to new reviews or chats, run your agent on a schedule.
Does it work with several locations?
Yes. list_locations returns every location your Podium user can open, and the Inbox, review, invite and payment tools take a location.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts use REST.
Is Cotlet affiliated with Podium?
No. Cotlet is independent and not affiliated with Podium Corporation.
Can I use the Podium API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.