Skip to main content
HelloLeo MCP works in two directions, and it helps to keep them apart. Inside HelloLeo, enabling it lets Leo (and your agents) reach your other projects: list them, read and edit their files, check their preview status and runtime errors, or look at what they are connected to. Useful when a new project should reuse a component you already built, or when the same change has to land on several projects. From outside HelloLeo, it turns your account into a remote MCP server. Connect it to Claude, Claude Code, Cursor or any MCP client and that assistant can create projects, write code, deploy previews and query your connected tools (Odoo and the rest), using your HelloLeo account.

​
Use it inside HelloLeo

1

Enable the integration

Open Project Settings → Project Integrations, pick HelloLeo MCP and save. There is nothing to fill in: HelloLeo issues the access for you.
2

Ask Leo about your other projects

“List my projects and tell me which ones already have an Odoo connection.”
3

Reuse what you built

“Copy the invoice table component from my Client Portal project into this one.”
Agents work the same way. Enable HelloLeo MCP on an agent and it can read and modify the projects its workspace gives it access to.

​
Use it from your AI client

Connecting an external AI client requires a plan that includes HelloLeo MCP (Leo Business and above). Enabling the integration inside HelloLeo works on every plan.
The server URL is:
You never paste a token anywhere. On first use the client opens a HelloLeo sign-in page, you approve the access, and the connection is bound to your account from then on.

​
Claude (web and desktop)

1

Add the connector

Settings → Connectors → Add custom connector, paste the URL above.
2

Connect

Click Connect. Your browser opens the HelloLeo consent screen, approve it.
3

Use it in a conversation

Enable the connector in the chat, then try “List my HelloLeo projects.”

​
Claude Code

The first tool call triggers the browser sign-in.

​
Cursor and other MCP clients

Add a remote MCP server (streamable HTTP transport) pointing at the URL above. Any client that supports remote MCP servers with OAuth will work the same way.

​
What the assistant can do

​
What it can and cannot reach

Every call is checked against your own permissions, on our side, not the client’s. An assistant connected to your account sees exactly the projects you see: the ones you own, plus those shared through a workspace you belong to. Anything else answers “not found”. A few things are deliberately out of reach, whatever the assistant asks for: environment files and secrets, the internal git directory, and HelloLeo’s own internal files. Requests are also rate limited, so a runaway loop cannot hammer your projects.

​
Troubleshooting

The client says the server is unauthorized. Sign in to app.helloleo.dev in the same browser, then reconnect. The consent screen needs an active HelloLeo session. Connecting fails and your plan is below Business. External clients are gated by plan. Enable the integration inside HelloLeo instead, or upgrade. A newly created project has no files. A blank project starts empty: ask the assistant to write its first file, then to deploy it. Preview URLs only appear once the sandbox has booted. Analytics come back empty. A project only has analytics once it has been previewed or published, and only page-level traffic is measured. Individual clicks are not tracked.