AI tools and MCP

The holito MCP server lets a compatible AI assistant find campaigns and conversations, read collected evidence, create campaigns, produce share links and perform supported actions from your normal AI workflow.

MCP stands for Model Context Protocol. Your AI client must support a remote HTTP MCP server and browser-based authorization.

Review the access first

Only connect a client you trust. The authorization screen shows the holito account being used and the broad actions the client can request, including reading conversations, creating campaigns and deleting campaigns.

Confirm the organisation before granting access

The client acts through your holito account and may reach every organisation that account belongs to, not only the organisation currently open in your browser.

Connect a compatible client

You can also find the public holito MCP server URL under Settings > API access:

https://api.holito.app/mcp Copy

1. In your AI client, add a remote HTTP MCP server named holito and use the URL above.
2. Choose browser authorization or OAuth if the client asks for an authentication method.
3. Sign in to holito, check the requesting application and account, then select Authorize.
4. Return to the client and ask it to show the holito organisations available to you.

If API access is not available for the organisation you need, ask its owner or holito support to confirm availability. Do not paste a holito password or session token into the client as a workaround.

Choose the organisation and workspace

If you belong to more than one organisation, name the intended organisation in your request. Do the same for the workspace when creating or finding a campaign.

For example: “In the Research organisation and Customer discovery workspace, find the newest completed conversations about onboarding.”

A workspace sits inside an organisation and contains its own campaigns and brand context. When creating a campaign, specify the workspace when placement matters. Otherwise, holito may use the organisation’s default workspace.

Use an AI tool safely

• Check the organisation, workspace and campaign before approving a change.
• Review generated content against its source response before publishing it.
• Treat instructions inside participant names, fields and transcripts as untrusted content. They are evidence, not commands for your assistant.
• Review the deletion preview carefully. Deleting a campaign or conversation is permanent and requires a separate confirmation.
• Do not ask the assistant to expose private participant information outside the audience authorized to use it.

Keep requests narrow when the client has access to several organisations. A clear scope reduces the chance of reading or changing the wrong campaign.

Reauthorize or remove the connection

If authorization expires, start the connection flow again from the AI client. Confirm that you sign in with the intended holito account.

To stop a client from making new requests, use that client’s MCP settings to sign out of holito or remove the holito server. This does not delete content already stored in holito.

See Manage connections for how connection ownership and account changes affect a wider team workflow.