Tailor.ia · Model Context Protocol
Tailor.ia MCP: your entire operation, inside the most advanced AI on the market
Query leads, reports and conversations, and manage the CMS in plain language, straight from Claude, Codex or Cursor. Authenticated per user, isolated per client.
MCP Endpoint
https://mcp.tailor.ia.br/mcp
Before you start
What you need
Tailor.ia is a remote MCP: nothing to install locally and no token to paste by hand. You connect the endpoint and sign in with your Tailor.ia account.
Tailor.ia account
Your Tailor.ia email and password. It is the same login as the dashboard.
An MCP host
Claude (Desktop, Code or web), Codex, Cursor or any client that speaks MCP over HTTP.
Nothing else
No Docker, no API key, no network setup. Login refresh is automatic.
Step by step
Connecting takes under two minutes
Pick the client you use. The endpoint is the same for all of them; only where you paste it changes.
Interface-based flow, no config files to touch.
- 01
Open Claude Settings and go to Connectors.
- 02
Click "Add custom connector".
- 03
Paste the Tailor.ia MCP endpoint into the URL field:
endpointhttps://mcp.tailor.ia.br/mcp - 04
Confirm. Claude opens the Tailor.ia login in your browser.
- 05
Sign in with your Tailor.ia email and password and authorize access.
- 06
Go back to Claude. The connector shows as connected and the Tailor.ia tools are now available in the conversation.
Once connected
What you ask for in plain language
The AI queries your operation at the source, instead of waiting for someone to export a spreadsheet and paste it into the chat.
Leads
Query your database in plain language
Ask who came in today, which campaign they came from, what stage they are in and what is still pending — without opening the dashboard or building a filter.
Reports
Operation numbers on demand
Support volume, conversion by stage, performance by period. The AI pulls the data and writes the analysis with it.
Conversations
Support history as context
Retrieve what was said in a specific conversation and use it to draft a follow-up, summary or escalation.
CMS
Content management from the chat
Query and manage published content right from the chat, without switching tools mid-task.
Access and isolation
The AI inherits the person's permissions, not a master key
Authenticated per user
Each person signs in with their own Tailor.ia account. The AI sees exactly what that user would already see in the dashboard, nothing more.
Isolated per client
Context is scoped to the client of the authenticated account. There is no path to another operation's data.
No keys to manage
No token pasted by hand, nothing in a text file. The session renews itself and you revoke access from the host itself.
FAQ
Questions about Tailor.ia MCP
MCP (Model Context Protocol) is an open standard that lets an AI model talk to external systems in a structured way. Instead of copying and pasting data into the chat, the model queries the source directly through tools exposed by the MCP server.
No. Tailor.ia MCP is remote: you just point the host at the endpoint and sign in. There is no Docker, no local runtime and no dependency to keep updated.
It works with any host that supports MCP over HTTP with authentication. We tested and documented Claude Desktop, Claude on the web, Claude Code, Codex and Cursor. Other compatible clients usually work when pointed at the same endpoint.
What the AI can do depends on the authenticated user's permissions. Read queries (leads, reports, conversations) are the main use case; write actions follow the same permission rules the user has in the dashboard.
Anyone with access to the Tailor.ia dashboard. Each person connects with their own login, and the data scope follows their profile.
From the host itself: remove the connector in Claude or the server in Cursor's mcp.json. On the Tailor.ia side, deactivating the user ends access immediately.
Your operation already has the data. The AI just needs to reach it.
If your Tailor.ia account does not have MCP enabled yet, talk to our team and we will activate access for you and your team.