Use Met from Claude in 3 steps
Connect Met to Claude without code or an API key and ask it to answer, look up and build. Also in Claude Code, Codex, Cursor and VS Code.
Claude can work inside your Met account, and so can Claude Code, Codex, Cursor, VS Code or any assistant that speaks MCP. You write to it the way you would write to someone on your team («which chats haven't I answered?», «create an orders collection») and it does it in Met for you.
You don't need to code or create an API key: you paste an address, sign in to Met and approve the permissions.
Step 1 · Add Met as a connector
The Met server address is always the same:
https://api.met.meteor.com.co/api/v1/mcp
The connector name is met- followed by your workspace name, for example met-my-company. In Met, Settings → Developers → Connect assistant gives it to you ready to copy, along with the commands for each assistant. That way, if you manage several workspaces, you connect one per workspace: each connector signs in separately and they don't clash.
Where you paste it depends on your assistant.
Claude (web or desktop app)
In Settings → Connectors, tap Add custom connector, give it the name Met gives you (for example met-my-company) and paste the address. If your Claude account is Team or Enterprise, an Owner of the organization adds the connector for the whole team. You don't need to touch claude_desktop_config.json: that file is for local servers.
Claude Code
In the terminal, add Met for all your projects:
claude mcp add --transport http --scope user met-my-company https://api.met.meteor.com.co/api/v1/mcp
Then open Claude Code and type /mcp to sign in, or do it from the terminal with claude mcp login met-my-company. Replace met-my-company with the name Met gives you.
Codex
In the terminal, add Met and sign in. You no longer need mcp-remote:
codex mcp add met-my-company --url https://api.met.meteor.com.co/api/v1/mcp
codex mcp login met-my-company
VS Code
In the terminal, add Met. VS Code asks you to sign in the first time you use it:
code --add-mcp '{"name":"met-my-company","type":"http","url":"https://api.met.meteor.com.co/api/v1/mcp"}'
MCP server also has the button that installs it in one click.
Cursor
MCP server has the button that installs it in one click. If you'd rather do it by hand, add a new server in Settings → MCP, or paste this into .cursor/mcp.json:
{
"mcpServers": {
"met-my-company": { "url": "https://api.met.meteor.com.co/api/v1/mcp" }
}
}
Other assistants
Any assistant that speaks remote MCP connects with the same address and the same name; ChatGPT, for example, adds it in Settings → Apps & Connectors, with developer mode on depending on your plan.
Step 2 · Sign in and approve the permissions
When you connect, your assistant opens a Met window. Sign in with your usual user and review the list of what the assistant will be able to do: read contacts, send messages, create flows, and so on. If you agree, tap Authorize.
- The assistant works on the workspace you have open in your session. If you manage several, switch to the one you want to connect first.
- Met never hands your password to the assistant. The session renews itself, so you don't have to sign in again every day.
- You can remove its access at any time in Settings → Developers → Authorized apps. The cut is immediate.
Step 3 · Ask for what you need
Write in your own words. You don't need to know what each tool is called: the assistant picks the right one and, if there is no specific tool for what you ask, it looks up the Met operation that does it and uses it with the same permissions you approved.
For day-to-day work
- «Which conversations haven't I answered since yesterday?»
- «Find Laura Gómez in my contacts and tell me what she last wrote to us.»
- «Reply to Laura that her order ships tomorrow morning.»
- «Schedule a reminder for Carlos on Friday at 10 a.m. about the quote.»
- «Hand Andrés's chat to someone on the team and tag it as *Complaint*.»
- «How much Energy do I have left, and which Met is spending the most?»
For building
- «Create a Met that answers questions about my product catalog, in a friendly tone, and hands the chat to a person when someone asks about warranties.»
- «Build a flow that, when a new lead comes in, tags it as *New* and lets me know.»
- «Create an *Orders* collection with the fields customer, product, amount, delivery date and status.»
- «Schedule an automation that sends me the pending orders summary every Monday at 8 a.m.»
- «Show me the templates I can install and tell me what each one would create.»
A new flow stays as a draft: the assistant builds it, can test a single step and asks you before publishing it. Until it is published, it doesn't trigger on its own.
For building your SDR (the Met that qualifies your leads, follows up with them and hands your team the ones that belong to it)
- «Create the contact fields *estado_relacion* (list: In discovery, Qualified, Not qualified, Meeting booked), *urgency* and *do_not_contact*.»
- «Show me Sara's follow-ups in the flow that handles my WhatsApp and add one at 2 hours, only if she isn't qualified yet, counting business hours only.»
- «Declare rule TH-1 on Sara: hand off to an advisor when the lead wants to buy more than one property. Tell me if any rule in her prompt would be rejected.»
Follow-ups are changed in the flow's draft without touching the rest of its steps, and they start running when you publish. Handoff rules are checked against the Met's prompt: if the prompt cites a rule that isn't declared, the assistant tells you, because that handoff wouldn't happen and the chat would stay with the Met.
Creating contact fields is a new permission («Create, edit and delete contact fields and variables»). If you connected your assistant before November 21, 2026, disconnect Met and connect it again to approve it.
For your pages and presentations
- «Open the brief *brief-branding-vikta-fit* and tell me which questions are still unanswered.»
- «With what we discussed in the meeting, fill in the brief's answers and show them to me before saving.»
The assistant reads the page's text —each answer box with the question next to it— and changes only the text: it doesn't move, delete or restyle anything. It doesn't publish either: it writes on pages that aren't published yet, and leaves a published one alone. The previous version stays in the page's history in case you want to go back.
What it asks you before doing
Some actions Met won't allow without your explicit confirmation: the assistant has to ask you first, and only goes ahead if you say yes.
- Deleting anything: a flow, an automation, a collection, a field, a record.
- Publishing a flow: from that moment its triggers use the new version.
- Replacing something that already exists: overwriting a flow's draft or an integration's credentials.
- Doing a lot at once: installing a template, importing contacts or records in bulk, tagging many contacts, creating a broadcast.
- Running a scheduled automation right now, outside its schedule.
What costs money
Every tool that spends says so, and the assistant warns you before using it:
- WhatsApp templates and broadcasts: every message has a cost with Meta and reaches a real person. The assistant confirms the template and the recipient with you, and can show you the message exactly as it will go out before sending it.
- Energy: running a Met, testing a flow step or running an automation spend Energy, just like when they happen on their own.
Creating or editing Mets, flows, collections and records doesn't spend Energy. Neither does looking things up.
On top of that, your assistant can ask for your permission every time it is about to use a Met tool. You set that up in the assistant's own settings.
There is one thing the assistant won't do even if you ask: talk over your team. If a person is handling a chat —autopilot is off or paused, or the contact asked to talk to a human—, the message isn't sent and the assistant tells you so.
What you can't do from the assistant
- Upload files: images, PDFs or documents are uploaded from the Met app. The assistant can still find the files you already have and give you their name and link.
- See secrets: API keys, integration credentials or signing secrets never reach the assistant. It can store a credential you give it, but not read it back afterwards.
- Buy or change plans: topping up Energy, adding add-ons or changing plans happens in the app. The assistant can tell you how much you have left and where it's going.
If your plan expired, the assistant can keep looking things up (contacts, conversations, data), but it can't change anything until the account is up to date. It tells you so instead of trying over and over.
If something doesn't work
- What you ask for doesn't show up: every permission you didn't approve leaves its tools out. Disconnect Met in your assistant, connect it again and approve what's missing.
- It works on the wrong workspace: remove its access in Settings → Developers → Authorized apps, open Met in the right workspace and connect again.
- You want the technical detail —connecting with an API key, the tools by area, how each one behaves—: it's in MCP server.