Claude connector
Connect LiveContext to Claude (claude.ai, the desktop and mobile apps) with your LiveContext sign-in. Claude can then browse your automations, run your workflows and applications, and add or edit table rows, while building stays in LiveContext.
Overview
The Claude connector is a remote MCP server at https://livecontext.ai/mcp/connector that you connect from Claude's connector directory. You sign in with your LiveContext account, so there is no key to copy. It is a lighter, sign-in based companion of the MCP server, which other MCP clients reach with an API key.
The connector operates what you already built: it reads the details of your workflows, applications, agents, tables, interfaces and skills, starts and stops runs, and writes table rows. It does not build or change automations, and it returns no content: no run outputs, no table rows, no mail, no file contents and no agent conversations. A run started from Claude answers with its id and status; open it in LiveContext to see what it produced.
Before you begin
- A LiveContext Cloud account with the workflows, applications or tables you want Claude to use. If you create your account from the sign-in page Claude opens, open LiveContext once and finish the welcome steps first: until then your account has no workspace for Claude to work in.
- A Claude account that can add connectors. On a Claude Team or Enterprise plan, an Owner of your Claude organization may need to add the LiveContext connector first.
- If you sign in to LiveContext through your company's single sign-on, sign in to LiveContext in the same browser first: the sign-in page Claude opens offers email and password, Google and GitHub only.
Connect LiveContext to Claude
- Find LiveContext in ClaudeIn Claude, open the connector directory (Customize > Connectors), find LiveContext and select Connect.
- Sign in to LiveContextSign in on the LiveContext page that opens, with email and password, Google or GitHub. If you are already signed in to LiveContext in this browser, this step is skipped.
- Allow accessA consent screen lists the access Claude asks for, including your profile, your email address, and offline access, which keeps the connection alive between conversations. Select Yes once, then wait: Claude takes a few seconds to finish connecting.
- Use it in a conversationAsk Claude, for example, “List my LiveContext workflows” or “Run my weekly report workflow” or “Add a row to my leads table with this contact”. When a tool needs your approval, Claude shows its name and waits for you.
In Claude (Customize > Connectors > LiveContext) you choose, for the read-only tools and for the tools that change things, whether Claude may use them freely, must ask your approval each time, or may not use them at all.
Claude works in the workspace you last switched to in the LiveContext app (your personal workspace unless you switched, see Organizations & roles). To have Claude work on another workspace, switch to it in the app: Claude follows from its next request.
What Claude can do
Claude lists the tools in two groups: the read-only tools, and the tools that run or change things.
| Tool | What it does |
|---|---|
| Browse workflows | Lists your workflows, shows one (its triggers, its pinned production version and the inputs a run needs) and lists its runs with their status and timings. |
| Browse applications | Lists your applications, shows one and lists its runs. |
| Browse agents | Lists your agents and shows one, with their budgets, departments and recurring tasks. |
| Browse tables | Lists your tables and shows their columns. It never reads the rows. |
| Browse interfaces | Lists your interfaces and shows one. |
| Browse skills | Lists your skills and their folders, and shows one. |
| Search the API catalog | Searches the integrations LiveContext can call and shows what an endpoint returns. |
| Tool | What it does |
|---|---|
| Run or stop workflows | Runs a saved workflow, as saved or as its pinned production version (see Versions and production), with the inputs you give, and stops a run that is executing. Stopping ends that execution only; the workflow keeps its schedules. |
| Run or stop applications | Runs one of your applications, with the inputs you give, and stops one of its runs. |
| Add, edit or delete table rows | Adds rows (or updates the row whose value matches, when you name a column to match on), edits the rows that match a condition, and deletes the rows that match a condition. A row change can start workflows that a table trigger watches. |
A run started from Claude acts on the services your workflow or application is connected to, exactly as if you started it in LiveContext, and it uses credits the same way (see Plans & billing).
Disconnect Claude
Any of these ends the connection, and you connect again from Claude to use LiveContext there. Signing out of the LiveContext app alone does not disconnect Claude.
- In Claude, disconnect LiveContext from your connectors.
- In LiveContext, when another browser or device is signed in, go to Settings > Overview > Security and select Sign out all other devices. It also disconnects every AI assistant connected to your account (see Account & settings).
- Change your LiveContext password (accounts that sign in with email and password): connections made before the change end. If you sign in with Google or GitHub, change the password there, then sign out all other devices.
Claude may keep access for up to 15 minutes after you sign out your other devices or change your password, the time its current access lasts. A connection also ends on its own after 14 days without use, and after 90 days in any case. Reconnect from Claude when that happens.
Troubleshooting
| What you see | What to do |
|---|---|
| Claude says authorization with LiveContext failed | Select Connect again, sign in, and select Yes on the consent screen (No refuses the connection). |
| An error page instead of Claude after the consent screen | It may have gone through. Close the page, open Claude and check the LiveContext connector; connect again only if it is not connected. |
| Claude reports a timeout after starting a run | Check the runs of that workflow or application before asking again: the run may have started, and a second request starts a second run. |
| Claude says it cannot do something and points you to LiveContext | The action is not available through the connector (building, approving, sharing). Do it in the LiveContext app. |
| A run started but Claude shows no result | The connector returns a run id and status only. Open the run in LiveContext to see its outputs. |
| Claude does not find a workflow you see in LiveContext | It is probably in another workspace. Switch to that workspace in the LiveContext app, then ask Claude again. A new account needs its welcome steps finished first. |
Still stuck? Write to [email protected]. How LiveContext handles your data is described in the privacy policy.