Every AI tool connects to livedocuments the same way: you give it one address, and the first time it uses it, you approve the connection on a livedocuments page. This article walks through that for the tools people use most. For what the AI can do once it is connected, see Connect an AI Tool (MCP).
You need a livedocuments account: connecting an AI tool is a signed-in-only feature.
The Address
livedocuments's MCP server lives at:
https://mcp.livedocuments.app/mcp
It is a remote MCP server over HTTP (what some tools call "Streamable HTTP"), so there is nothing to install or run on your computer. Wherever a tool asks for a connector, a remote MCP server or a server URL, this is the address to give it.
Approving the Connection
The first time your tool connects, it opens a livedocuments page in your browser:
Check the page. It is titled Connect followed by your tool's name, and it says which site the access will be sent to. Only continue if you recognise that site.
Switch on Read-only access if the tool should only find and read your documents, never change them.
Choose Connect. The browser hands you back to your tool, and the connection is ready.
Approving creates an API token named after the tool, which you can revoke on liveworkspace.app to disconnect it. It lasts six months; reconnect the tool after that.
Claude
In Claude on the web, open Settings, then Connectors, and add a custom connector. Give it a name such as "livedocuments", paste the address above as its URL, and add it. Then choose to connect it, and approve the connection on the livedocuments page that opens.
On a Team or Enterprise plan, an owner of your Claude organisation may need to add the connector before members can connect it. Exact menu names in Claude can change between versions; look for custom connectors in its settings.
Claude Desktop
Claude Desktop uses the same connectors as Claude on the web: a connector you add there appears in the desktop app when you are signed in to the same Claude account, and you can add one from the app's own Settings, Connectors in the same way. Approve the connection when the livedocuments page opens in your browser.
Claude Code
Add the server from your terminal:
claude mcp add --transport http livedocuments https://mcp.livedocuments.app/mcp
Then, in a Claude Code session, run /mcp, choose livedocuments, and authenticate: your browser opens the livedocuments approval page. Add --scope user to the claude mcp add command to make livedocuments available in every project rather than only the current one.
If you'd rather use an API token than sign in through the browser, pass it as a header instead:
claude mcp add --transport http livedocuments https://mcp.livedocuments.app/mcp \
--header "Authorization: Bearer lwt_..."
For coding agents working in a repository, the livedocuments CLI is an alternative to the MCP server: both use the same API and the same kind of token.
Cursor
Add livedocuments to Cursor's MCP configuration: ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project.
{
"mcpServers": {
"livedocuments": {
"url": "https://mcp.livedocuments.app/mcp"
}
}
}
Cursor then lists livedocuments in its MCP settings and offers to sign in to it, which opens the livedocuments approval page. To use an API token instead, add a headers entry beside url:
"headers": { "Authorization": "Bearer lwt_..." }
ChatGPT
Where your ChatGPT plan lets you add custom connectors (it is part of ChatGPT's developer mode, and the wording varies by plan and version), create a new connector, paste the address above as its MCP server URL, and choose OAuth for authentication. Approve the connection when the livedocuments page opens.
Any Other MCP Client
Any tool that supports remote MCP servers can connect. Add a remote server (HTTP) with the address above. If the tool supports signing in to servers (OAuth), it finds livedocuments's sign-in by itself: there is no client id or secret to enter. If it doesn't, use an API token, below.
Using an API Token Instead
Some tools can't sign in to a server, or you may want to set one up from a script or a config file. Instead of approving the connection in the browser, you can give the tool an API token as a header on every request:
Authorization: Bearer lwt_...
Create a token on liveworkspace.app (see API Tokens), and copy its secret: it is shown once.
In your tool, add the MCP server with the address above, and set the Authorization header to
Bearer followed by a space and the secret.
Switch on Read-only when you create the token if the tool only needs to look. Treat the secret like a password, keep it out of files you share or commit, and revoke the token when you stop using the tool.
If It Doesn't Connect
- The page says "This link has expired" or "This request has expired": a connection request lasts ten minutes. Start the connection again from your tool.
- It says your account has reached its limit of API tokens: you can have 20 unexpired tokens. Revoke one on liveworkspace.app, then connect again.
- The tool keeps asking you to sign in: the token it held may have expired or been revoked. Remove the connection in the tool and add it again.
Was this article helpful?