The agency's portfolio inside Claude, ChatGPT and Grok.
Imofolio exposes an MCP server. Connect the assistant your team already uses to the agency's real properties, listings, contacts and searches — read-only, one organisation per key, all in English.
Works with
https://app.imofolio.com/api/mcp{
"mcpServers": {
"imofolio": {
"type": "http",
"url": "https://app.imofolio.com/api/mcp",
"headers": { "Authorization": "Bearer csk_…" }
}
}
}One protocol, every assistant
MCP (Model Context Protocol) is the standard connection between a model and the data it uses. Imofolio speaks that protocol, so there is no new integration to build whenever your team changes assistants.
One endpoint, many clients
The same server responds to Claude, ChatGPT, Grok, Cursor and any automation that speaks MCP. No exports, no copies.
Read-only by design
All eight tools are marked readOnly and none can write. The assistant can read the portfolio; changes remain your work in the CRM.
Live data, not a PDF
Every question queries the database in real time. Prices, availability and listing status are exactly what the agency sees in its dashboard.
Three steps, five minutes
Generate an organisation key
One csk_… key per team or automation, with expiry and immediate revocation. Only the cryptographic hash is stored — the plain-text key appears once.
Point the client to the endpoint
In Claude web, add the connector and authorise with your Imofolio account. In other clients, paste the endpoint and key into the Authorization header.
Ask in English
The client discovers the tools on its own. Your team writes naturally and the assistant chooses the right query, with European Portuguese enums and labels.
Where it already works
Any client that speaks MCP over HTTP. These are the ones teams commonly use.
Claude
OAuthClaude Code
KeyChatGPT
KeyGrok
KeyCursor and VS Code
Keyn8n and other automations
Keyclaude mcp add --transport http imofolio https://app.imofolio.com/api/mcp \ --header "Authorization: Bearer csk_…"
The portfolio stays put
Connecting a model to agency data is only acceptable with explicit boundaries. Here they are.
Tenant locked on the server
The organisation is resolved from the key or OAuth token and fixed on the server. No tool argument can request data from another agency.
Read-only, nothing else
There is no tool that creates, changes or deletes. A confused assistant cannot damage the portfolio.
Keys with expiry and audit trail
We store only the key's SHA-256 hash. Each key has a scope, optional expiry, last-used date and immediate revocation.
OAuth consent
In Claude web, the connection goes through your account and the organisation you choose, with the same roles and permissions as the CRM.
No training on your data
Imofolio does not use agency data to train models. What the assistant reads stays between the agency and the provider you choose.
Data in the European Union
Database and files hosted in the EU, with organisation-level isolation in the database and a data processing agreement available.
What if the team would rather stay in the CRM
Imofolio's assistant runs inside the app, with the same MCP tools and the context of the screen you are on. It suits people who prefer asking where they already work — MCP is for those who live in Claude, ChatGPT or an automation.
- Answers with links to the property, listing or contact
- The same permissions as the questioner's session
- Included in every plan, with monthly credits
Ask in EnglishThe assistant reads the portfolio, listings and agency contacts.
Questions about the connection
Connect the assistant to the real portfolio.
Create your account, import your properties and ask your first question from the assistant your team already uses.
