Perfect Venue MCP Server

Events, leads, proposals and payments for your Perfect Venue venue.

Servidor MCP alojado

npx add-mcp 'https://cotlet.dev/mcp/v1/perfect-venue'

Se instala en Claude Code, Codex, Cursor y más

Documentación

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Perfect Venue API and MCP server: Let your AI agent work your private event leads.

Perfect Venue has no MCP server and no public API for venue teams (checked 27 Oct 2026). Its REST API goes to integration partners who ask eng@perfectvenue.com for an OAuth app, and the only self-serve endpoint takes leads from a website form on Enterprise. Cotlet runs 14 Perfect Venue tools hosted, over MCP for agents and REST for scripts.

Events, leads, proposals and payments for your Perfect Venue venue. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Perfect Venue. Perfect Venue is a trademark of its owner. If Perfect Venue's own integrations cover what you need, use them first.

What can you automate in Perfect Venue?

  • Follow up on leads that went quiet
  • Add emailed and phoned inquiries
  • Send the proposal after your OK
  • Chase balances due
  • Log checks and cash
  • Count new leads and bookings

Does Perfect Venue have an MCP server or an API?

  • The partner API (version 1.3.0, 18 Jun 2026) lists, creates and edits events and contacts and sends 4 webhooks. It cannot change a status, send a proposal or email, or touch payments.
  • Zapier has 3 triggers and 2 actions: Create Event and Get Event Details. Zapier MCP offers the same 2. n8n has no Perfect Venue node.
  • Event Assistant drafts guest replies on every plan, but only the first reply to a new inquiry can go out by itself, and no outside agent can call it.
What you needZapierPartner APICotlet
Create a leadYes, Create EventAfter approvalYes
List and edit eventsRead one by IDAfter approval, no statusYes, status too
Read the Inbox, send emails and proposalsNoNoYes, after your OK
Payments, balances and refundsNoNoYes
Use from Claude, n8n or a script2 actions in Zapier MCPYour own codeYes

Checked 27 Oct 2026. Sources: Perfect Venue Help: Leads API (Enterprise Feature), Perfect Venue pricing and plans, Perfect Venue on Zapier, Perfect Venue REST API docs (partners), Perfect Venue Help: Event Assistant with AI Reply

How does Cotlet connect to Perfect Venue?

  1. Sign in to Perfect Venue. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Perfect Venue password, and no email, proposal or refund reaches a guest until you approve it.

Connect Perfect Venue 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.

  1. Enable Perfect Venue for agents. Create a Cotlet account, sign in to Perfect Venue in its Cloud Browser and press Enable for agents.
  2. Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
  3. Authorize it. Chat apps send you through a Cotlet sign-in. n8n, editors and scripts take an API key from the console.

Perfect Venue sits on the same address, https://cotlet.dev/mcp/v1, as every other app you enable. Turned Perfect Venue on after you connected? Refresh the connector to load its tools.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-perfect-venue \
  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-perfect-venue": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-perfect-venue]
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: perfect_venue_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: perfect_venue_write

How to use the Perfect Venue REST API

Create your Cotlet API key

Create a Cotlet API key with access to Perfect Venue and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Perfect Venue in Cotlet and enable it for agents. Account access: Your own Perfect Venue account (Admin or Editor to change events; Viewer and Limited View are read only).

Make your first Perfect Venue API request

REST:

curl https://cotlet.dev/api/v1/perfect-venue/events \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read events 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": "perfect-venue",
  "tool": "list_events",
  "result": {
    "events": [
      {
        "event_id": "ev_8812",
        "name": "Smith rehearsal dinner",
        "status": "confirmed",
        "start_date": "2026-11-14",
        "start_time": "18:00",
        "end_time": "22:00",
        "group_size": 40,
        "spaces": [
          "Private Room"
        ],
        "owner": "maria@example.com",
        "contact": {
          "name": "Jane Smith",
          "email": "jane@example.com"
        }
      }
    ],
    "next_cursor": null
  }
}

Lists events from your account, including leads. Filter by status (lead, qualified, proposal_sent, confirmed, balance_due, completed or lost), by event date, by venue and by event owner.

Each item has the event ID that the other tools take. Lost events are returned only when status is lost, as they are hidden from the home stages in the app.

from: Only events on or after this date.

to: Only events on or before this date.

limit: Events per page.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Perfect Venue workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestOne event with dates, spaces, guests, contact, status, notes, proposal totals and whether the proposal is locked. Use get_event in your configured business report.
MakeHTTP > Make a requestPayments of one event: deposits, scheduled payments and offline payments, with amount, method and date. Use list_payments in your configured business report.
Python or Node.jsREST APIOne line per event, like Reports, Events: status, owner, dates and the sales breakdown. Use get_events_report 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 Perfect Venue; 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.

Perfect Venue API endpoints and MCP tools

Events, leads and spaces

Lost events come back only when you ask for status lost. Editing needs an Admin or Editor role; Viewer and Limited View only read.

  • List events (list_events, read): Events and leads with status, dates, guest count, contact and event owner.
  • Get event (get_event, read): One event with dates, spaces, guests, contact, status, notes, proposal totals and whether the proposal is locked.
  • List spaces (list_spaces, read): The spaces of your venue with their IDs.
  • Create lead (create_lead, write): New inquiry in the Lead status with its contact. Nothing is sent to the guest.
  • Update event (update_event, write): Change date, time, guests, spaces, event type, owner or internal notes of an event.
  • Set event status (set_event_status, write, asks first): Move an event to another status, with a lost reason when it is lost.

Inbox, templates and proposals

Emails go out from the event thread, so the guest's answer lands on the same event. A sent proposal moves the event to Proposal Sent by itself.

  • List messages (list_messages, read): The inbox thread of one event: emails to and from the contact with time and text.
  • List email templates (list_email_templates, read): Your template emails from Settings, Email, with name, subject and text.
  • Send email (send_email, write, asks first): Email the event contact from the Perfect Venue inbox, from your text or a template.
  • Send proposal (send_proposal, write, asks first): Send the event proposal to the guest, where they review it, sign and pay the deposit.

Payments and reports

Only online payments can be refunded; offline ones go back by cash or check. A refund takes 5 to 7 business days to reach the guest.

  • List payments (list_payments, read): Payments of one event: deposits, scheduled payments and offline payments, with amount, method and date.
  • Log offline payment (log_offline_payment, write, asks first): Record a cash, check or in-house card payment on an event.
  • Refund payment (refund_payment, write, asks first): Refund an online payment in full or in part, with a reason.
  • Get events report (get_events_report, read): One line per event, like Reports, Events: status, owner, dates and the sales breakdown.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/perfect-venue-api-mcp-server#tools

Who can see my Perfect Venue session, and how do I revoke it?

  • What we store. Your signed-in Perfect Venue profile, AES-256-GCM encrypted, kept in Finland. No password.
  • What your agent gets. The 14 Perfect Venue tools, never the cookie.
  • What the session sees. What your role sees: events, guest contacts, Inbox threads, payments.
  • What no tool touches. Settings, team members, your plan, payouts and deleting events.
  • If Perfect Venue signs you out. We email you a sign-in link. You sign in, we never do.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.

cotlet.dev scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Pulls open events. Lead, Qualified and Proposal Sent, past dates dropped.
  2. Reads each thread. If the guest wrote last, it goes on your reply list.
  3. Waits for your OK. Each follow-up email shows up in your Cotlet console.
  4. Reports back. Sent, skipped and suggested for Lost, with dates.
ActionUndo
Send an email or a proposalNo, it is in the guest's inbox
Refund an online paymentNo, the money goes back to the guest
Move an event to LostSet the old status again; stage emails may have gone
Create a leadMove it to Lost
Edit event detailsSame tool with the old values

5 of 14 tools ask first: the ones that email a guest, change a status or move money. New leads and event edits reach nobody, so they run at once. Switch the wait off per tool for a scheduled run.

A proposal locks by your locking rule, at signing or one or two weeks before the event. get_event says whether it has.

MCP call:

{
  "name": "create_lead",
  "arguments": {
    "first_name": "Alex",
    "last_name": "Client",
    "email": "client@example.com",
    "start_date": "2026-11-14",
    "start_time": "18:00",
    "end_time": "22:00",
    "group_size": 40,
    "event_type": "Birthday",
    "message": "Birthday dinner, needs a private room."
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/perfect-venue/leads \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Alex","last_name":"Client","email":"client@example.com","start_date":"2026-11-14","start_time":"18:00","end_time":"22:00","group_size":40,"event_type":"Birthday","message":"Birthday dinner, needs a private room."}'

Response:

{
  "event_id": "ev_8841",
  "status": "lead",
  "start_date": "2026-11-14",
  "group_size": 40,
  "contact": {
    "name": "Alex Client",
    "email": "client@example.com"
  }
}

Scripts and cron jobs call the same tools over REST at /api/v1/perfect-venue, with one key and one price. An edit your Perfect Venue role cannot make fails and costs nothing. The tools table lists the REST path of each tool.

How much does the Perfect Venue MCP server cost?

About $31 a month for one restaurant booking about 16 private events a month, 5,340 credits. Perfect Venue still bills your plan as before.

JobCallsCredits
Follow up on quiet leads, daily8 × 302,400
Add emailed and phoned inquiries2 × 20400
Set details and send the proposal3 × 16480
Balance due reminders, weekly8 × 4320
Log checks and cash after events2 × 8160
New leads and bookings report, weekly2 × 480
Cloud Browser, 30 days1,500
Total5,340
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on the free Perfect Venue plan, no Enterprise needed

The month is our example: about 45 inquiries and 16 confirmed events, close to the "4+ events per week" in Perfect Venue's Meski story. The daily follow-up pass is most of it. Dollars at the $29 pack rate.

Perfect Venue MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Perfect Venue partner APIOAuth REST for venues, events and contacts, 4 webhooks, 100 requests a minute.Only for partners Perfect Venue sets up; no Inbox, proposals, statuses or payments.
Leads APIOne endpoint that turns your own website form into a lead.Enterprise plan, allow-listed website origins, write only.
Hostie, Slang AIAI phone answering that creates a Perfect Venue lead after an event call.Only creates leads; nothing works the leads already in your account.
GitHubNo Perfect Venue MCP server or CLI found.You would write it yourself on endpoints the terms do not allow.

If phone calls are where leads get lost, an AI receptionist feeds Perfect Venue. If you are a software vendor, ask Perfect Venue for partner access. If your team needs an agent that follows up, sends proposals and tracks balances in the account you already use, that is what Cotlet does.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and working since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Perfect Venue tools go to contact@cotlet.dev.

Perfect Venue API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Perfect Venue under Integrations in the console and sign in to Perfect Venue in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect Perfect Venue to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Perfect Venue 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 Perfect Venue account through Cotlet, in their phone apps too.

What can ChatGPT do in Perfect Venue?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Perfect Venue: follow up on leads that stopped replying; create leads from emailed and phoned inquiries; send balance due reminders before the event. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need the Enterprise plan?

No. Cotlet works in your own Perfect Venue account, on any plan, and does not use the Leads API, which Perfect Venue limits to the Enterprise plan. Changing events and sending proposals needs an Admin or Editor role; Viewer and Limited View roles cannot edit anything.

Does changing an event status email the guest?

It can. Perfect Venue sends automated emails by event stage, such as Lead or Confirmed, and each one can be switched on or off in Settings, Email. Confirmed is set by Perfect Venue itself when the guest signs the proposal or pays the deposit. set_event_status asks for your OK by default for this reason.

Does Perfect Venue have webhooks?

Only for partners: the partner API sends event created, status changed, deleted and new contact since June 2026. Zapier offers the same kind of triggers. Cotlet receives none of them, so run your agent on a schedule, for example a morning pass over new leads.

Will it clash with Event Assistant and AI Reply?

No. Event Assistant can send the first reply to a new inquiry by itself and drafts the rest inside Perfect Venue. Your agent reads the same thread, so it sees that first reply and skips leads where the guest wrote last.

Is the MCP server different from the REST API?

Only the way in. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Perfect Venue?

No. Cotlet is independent and not affiliated with Perfect Venue, P.B.C.

Can I use the Perfect Venue 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.