Connect your AI over MCP
Connect Claude, ChatGPT, Codex, or Cursor to Liteo, sign in once, and let it search, read, and update your workspace.
Liteo has an MCP server. Add it to your AI client, sign in to Liteo, and your AI can work in your workspace through named tools.
The server address
Liteo's MCP server lives at one address:
https://app.liteo.io/api/mcpOnce connected, it can search your contacts, businesses, and deals. It can read a customer's sites and installed products. It can draft a quote, record a service visit, and file tasks and notes. Tools are grouped by the records they work with.
2 ways to connect
- Sign in. You add the address, select Connect, sign in to Liteo, pick a workspace, and approve. This is how ChatGPT, claude.ai, and Claude Desktop connect. Claude Code, Codex, and Cursor can use it too.
- API key. For Claude Code, Codex, Cursor, and your own scripts. You keep the key in an environment variable, and the client sends it with every call.
Either way, your AI works as a member of your workspace. Its saved connection permissions also limit what it can read and change.
Connect ChatGPT
- In ChatGPT, turn on developer mode and add a new connector.
- Enter
https://app.liteo.io/api/mcpas the URL and choose OAuth as the authentication. - ChatGPT sends you to Liteo. Sign in, pick the workspace, and approve.
Connect claude.ai or Claude Desktop
- Open Settings, then Connectors, and choose Add custom connector.
- Enter
https://app.liteo.io/api/mcp. Leave the OAuth client fields empty. Claude registers itself. - Select Connect, sign in to Liteo, pick the workspace, and approve.
Liteo's approval screen shows which app is asking and where it sends you back. Check both before you approve.
Connect Claude Code, Codex, or Cursor
These clients can sign in the same way. Use an API key instead if you'd rather keep the connection in your own config.
Claude Code, from the terminal:
claude mcp add --transport http liteo https://app.liteo.io/api/mcpThen run /mcp in Claude Code and authenticate.
Codex reads ~/.codex/config.toml. The CLI, the IDE extension, and the desktop app share it:
[mcp_servers.liteo]
url = "https://app.liteo.io/api/mcp"Then run codex mcp login liteo.
Cursor reads ~/.cursor/mcp.json, or .cursor/mcp.json in a project:
{
"mcpServers": {
"liteo": { "url": "https://app.liteo.io/api/mcp" }
}
}With no key in the file, Cursor connects by sign-in.
Use an API key instead
Decide which kind of key the AI should use. Both are created in the same place.
- Personal key. Acts as you and stops working when your access ends. Right for your own Claude Code, Codex, or Cursor.
- Workspace key. Only admins can create one. New records land with the member you choose. It can't manage automations, forms or custom fields, or delete records permanently.
Create the key in Liteo:
- Open Settings, then AI & MCP.
- Choose Other.
- Select Create key.
- Name it after the client, such as Claude Code or Cursor, and choose the type.
- For a workspace key, choose who new records should land with.
- Copy the key before you leave the dialog.
Save it as an environment variable named LITEO_MCP_API_KEY, then point your client at it.
Claude Code, in a project .mcp.json. The file holds no secret, so it's safe to commit:
{
"mcpServers": {
"liteo": {
"type": "http",
"url": "https://app.liteo.io/api/mcp",
"headers": { "Authorization": "Bearer ${LITEO_MCP_API_KEY}" }
}
}
}Codex, in ~/.codex/config.toml:
[mcp_servers.liteo]
url = "https://app.liteo.io/api/mcp"
bearer_token_env_var = "LITEO_MCP_API_KEY"The Codex desktop app only sees variables from your login shell profile.
Cursor, in mcp.json:
{
"mcpServers": {
"liteo": {
"url": "https://app.liteo.io/api/mcp",
"headers": { "Authorization": "Bearer ${env:LITEO_MCP_API_KEY}" }
}
}
}Important
Keep the key private. It allows the reads and writes saved in its permissions. Liteo only shows it once. Revoke it when you stop using it. Team-wide MCP settings, such as Cursor Team MCP, give one key to everyone on the team. Use sign-in there instead.
Check the connection
Ask your AI "Which Liteo workspace are you connected to?" It runs get_workspace and answers with the workspace name and the member it acts as.
If your client limits how many tools it shows, load a subset: https://app.liteo.io/api/mcp?toolsets=crm,operations. The toolsets are crm, operations, catalog, commerce, automations, and forms.
Choose the connection's access
Open Settings → AI & MCP, find the connected app or key, then open Permissions. New API keys and first-time OAuth connections start with Standard access: read, create and edit. Read only turns changes off. Full CRM access includes Trash and Restore for every record type that has them. Custom lets you choose individual permissions, including Permanently delete.
Save the permissions on that connection. The access cards above the setup steps are a preview; choosing one doesn't grant access or set a default for the next app. Existing connections keep their saved grants. They don't gain new Trash, Restore or Permanently delete permissions automatically. Reconnecting the same registered OAuth app as the same member in the same workspace keeps its saved policy.
You can reduce your own connection's access. Only a current workspace admin can add access or manage workspace connections. Full access stays within the member's role and the tools that connection type supports. No preset grants permanent deletion; an admin ticks it per connection under Custom.
Your AI app may still ask you to approve a call. Those prompts are controlled by the client, separately from Liteo's saved grants.
What the AI can and can't do
- Available with the required saved permissions: search and read your CRM data, the catalog, sites, locations, installed products, service history, quotes, and invoices. Create and update contacts, businesses, deals, deal lines, sites, locations, installed products, and catalog items. Create notes and tasks, complete tasks, and add or remove contact tags. Record service visits and create draft quotes and invoices.
- Admins with the required saved permissions: read an automation in full, and create, change, turn on, or delete automations. Create, change, switch off, delete or restore forms. Rename custom fields, move them to Trash and restore them. Delete records in Trash permanently. Use a personal key or OAuth. Liteo checks the current admin role on every call.
- Needs
confirm: trueon the call: archiving a site, removing an installed product, deleting an automation or a form, and every permanent deletion. The call fails without it. This field is separate from your AI app's approval prompts. - Trash: a connection with Read and Trash can move a contact, deal, business, task, product, site, draft quote or draft invoice to Trash. Contacts and deals also need workspace enablement. Read and Restore allow recovery. Links and attachments stay in place. Active lists and ordinary reads omit the record; use the Trash tools to find it.
- Permanent deletion: an admin's connection with Read and Permanently delete can delete a record in Trash for good. It can't be undone.
- Stays in Liteo: sending, accepting, or issuing a quote or invoice. Recording a payment, voiding, or credit notes. Setting up webhooks, putting a form live.
Creating, changing, or turning on an automation also needs permissions for its trigger, referenced records, and actions. Checks include settings left unchanged in an update. For example, creating tasks needs Tasks Read/Create and Members Read.
Turning off, deleting, or reordering a rule needs its corresponding automation permission, without the action permissions. Saved rules run as workspace automations. Reducing the connection's permissions later doesn't stop them; turn off the rule to stop future runs.
Use a trash_* tool, such as trash_contact or trash_product, to move a record to Trash. Use the matching list_trashed_* tool to inspect saved summaries, then the restore_* tool to recover the record. Sites come back from Trash with restore_trashed_site; restore_site still un-archives a site. Existing connections need explicit grants for these operations.
Trash lists allow up to 50 rows per page and take an optional search. Restore checks the saved owner and links; it can need repairs. Missed reminders and automations don't run again. See the Trash API contract for retry keys, results and refusal reasons.
The purge_* tools, such as purge_deal, delete a record in Trash permanently. Each call deletes one batch. Repeat the call until the result says purged. See permanent deletion for what goes with each record and when Liteo refuses.
Reads work while your workspace has no active plan. Writes don't. The same request limits apply as for the REST API. Read the API reference for toolsets, pagination, and limits.
Disconnect a client
Open Settings, then AI & MCP.
- For a client that signed in, find it under Connected apps and select Disconnect.
- For a client that uses an API key, find the key and select Revoke key.
The client loses access right away. Nothing it already created is removed.
Related guides
Last updated on