model context protocol · live · works with any mcp assistant

Your customers, inside ClaudeChatGPTCursorChatGPT.

One link, and the assistant you already use can read every account through Meza, see what your agents found and drafted, and act on it with your yes. Same data. Same scope. No new tab.

connect urlhttps://mcp.meza.ai/mcp
Meza connected
three of the things people ask
what changes

When Meza is in the room

Your assistant stops guessing about customers and starts reading the record.

1

Nothing leaves Meza

Every answer is a live read of your own workspace, scoped to you. No export, no copy, no stale sync.

2

Not a chatbot bolted on

The assistant calls the same sixteen tools Ask Meza uses: health, renewals, tickets, meetings, the agents and their drafts.

3

Acts only with your yes

Reads are free. Approving a draft, running an agent or creating a task waits for your confirmation inside the assistant.

set up

Connected in a minute

Paste the URL, approve once, ask.

01

Claude

Settings → Connectors → Add custom connector → paste the URL → Approve.

02

ChatGPT

Settings → Connectors → Create → paste the URL → Approve. Team and Enterprise.

03

Cursor

Settings → MCP → Add new server → paste the URL → Approve.

Full walkthrough in the docs. Connected assistants show under Integrations in Meza, with Disconnect.

under the hood

Sixteen tools. The ones Meza itself uses.

find_accountsaccount_overviewhealth_scoresupport_ticketsmeetingsemailsconversationsrenewalslist_agentsagent_runapprovalsrun_agentdecide_approvalcreate_taskdraft_emailask_meza
scoped to you, recorded for you

Meet your customers where you already work.

Each connection is one person in one workspace. Every tool call lands in your activity log. Disconnect any time.