MCP
Set meiti up from Claude, Codex or Grok.
Through meiti's MCP server an AI sets up your assistants for you: skills, knowledge, business hours, forwarding and tests. You describe what you need — the client reads your setup, changes it and checks the result with tests.
/mcp/setup on meiti's MCP host — the app shows the exact addressAuthorization: Bearer <access token>, valid for 8 hoursWhat MCP does — and what it doesn't
| MCP | API | |
|---|---|---|
| What for | Setting meiti up: assistants, skills, knowledge, tests | Your software's daily work: messages, contacts, appointments, conversations |
| Who calls | an AI like Claude Code, in conversation with you | your system, permanently |
| Access | token from the app, valid for 8 hours | one API key per system |
- The client only works within its token's scope: one inbox — or, with an organisation-wide token, every inbox of your organisation.
- Every customer gets the same tool catalogue for setup, testing and improvement — however access was unlocked.
- Not via MCP: creating organisations or inboxes, buying or assigning phone numbers, unlocking features and reading live conversations. Ask the meiti team for those.
- Prompts, tests, contact details and results are customer data — the client treats them as such. Verifying a forward target stays your job.
Should your software send messages or create appointments? That's what the API is for.
Access in the app
- In the meiti app: Settings → Setup & operations → Connected systems → MCP server access. The entry appears once MCP is unlocked for you — on the Enterprise plan or on request for your organisation.
- The page shows the server URL and a fresh access token — both copied with one tap.
- If you are an owner or admin of the organisation, you can switch on “Organisation-wide access”: the client then sets up every inbox of your organisation, not just the current one.
- Pick the MCP client (Claude, Codex, Grok or Generic) and copy the command under “Connect” — server URL and token are already filled in.
- The token is a dedicated MCP credential, not your app sign-in, and is valid for 8 hours. After that, open the page again and connect with the new token.
- The token grants your access — keep it secret. If MCP is switched off for your organisation, tokens already issued stop working too.
Connect a client
Replace <server URL> and <access token> with the values from the app — or copy the ready-made command there.
Claude Code
Run in a terminal — connects Claude Code straight to meiti.
claude mcp add --transport http meiti-setup <server URL> --header "Authorization: Bearer <access token>"
Remove: claude mcp remove meiti-setup -s local
Codex
Run the whole command in PowerShell, then restart Codex. It stores the token for your Windows user and connects Codex to meiti.
[Environment]::SetEnvironmentVariable('MEITI_MCP_TOKEN', '<access token>', 'User'); codex mcp add meiti-setup --url <server URL> --bearer-token-env-var MEITI_MCP_TOKEN
Remove: codex mcp remove meiti-setup
Grok
Run in a terminal — connects Grok straight to meiti.
grok mcp add --transport http meiti-setup <server URL> --header "Authorization: Bearer <access token>"
Remove: grok mcp remove meiti-setup
Other clients
These values fit any client that supports remote MCP servers over Streamable HTTP.
Transport: Streamable HTTP
URL: <server URL>
Authorization: Bearer <access token>
Remove: Remove “meiti-setup” in your MCP client.
How the client sets up
The server gives every client the same way of working. So you can follow what it does:
- Read first: look at assistants, skills, features, business hours and forwarding before changing anything.
- An assistant is the persona: system prompt, greeting and attached skills. Before it goes live on a channel, the client sets up phone or chat for it.
- A skill is one task: create it, then set prompt, trigger and question limit one by one and attach it to the assistant. Questionnaires exist for chat, not for the phone.
- Set up voice, business hours and handover targets, then activate the finished assistant.
- Test and improve: run the preflight check, assistant tests and persona tests, read the results, sharpen, test again.
- If something genuinely isn't possible yet, the client reports it to the meiti team instead of working around it.
Tools
A client gets these tools with your token. It reads the exact parameters from the server itself.
| Area | What for |
|---|---|
| Account health and guided setup |
What the inbox still needs — and a step-by-step guide. WhatsApp first: the options with pros and cons, a recommendation (shared inbox on the landline, personal inbox via the WhatsApp Business App) and Meta's onboarding in order: business details, connecting, payment method, business verification.
5 tools
|
| Assistants |
Read, create, copy and set up assistants (bot profiles): system prompt, greeting, phone, chat and email, attaching skills, forward target, setup status and report.
17 tools
|
| Skills and handovers |
Create and sharpen skills — titles, prompt, trigger, question limit, conditions —, questionnaires for chat, approvals for appointments, handover targets and the callback note.
19 tools
|
| Standard replies |
Set the content, approval, guidance and skills of the standard replies.
4 tools
|
| Knowledge |
The knowledge the assistant answers from: maintain entries and create, import, enable and disable the organisation's knowledge collections.
8 tools
|
| Hours, phone and forwarding |
Business hours, forward targets, voice and phone settings, which assistant is active on the phone, and names of SIP devices.
11 tools
|
| Tests |
Write, generate and run assistant tests, read the results and turn passing tests into rules — also as a simulated phone call. Plus persona tests: simulated customer conversations in an isolated copy of your setup.
21 tools
|
| Decision rules and insights |
Read and delete decision rules, check their calibration and refresh the conversation outcome insights.
4 tools
|
| Inbox |
Which features are active in the inbox, and whether the chat sends read receipts.
2 tools
|
| Feedback to meiti |
Something isn't possible yet? The client reports it to the meiti team instead of working around it.
1 tool
|
| Organisation (organisation-wide token only) |
Read the whole organisation: every inbox with ids and channels. With an organisation-wide token the other tools also take a workspaceId to set up a specific inbox.
1 tool
|
MCP for your organisation?
We unlock access and are happy to set up the first assistant together with you.