Endless in other AI apps
Endless publishes a remote MCP server, so Claude, Cursor and VS Code can read your workspace — your assets, projects and chats — with your own sign-in.
Connectors bring other tools into Endless. This page is the other direction: your Endless workspace, read from the AI app you already have open.
Endless publishes a remote MCP server. MCP — the Model Context Protocol — is the standard an AI app uses to reach a system it doesn't own. Point a client at one address, sign in with your Endless account, and the assistant can search your assets, open a project and read a past chat while you're talking to it.
The address is the whole configuration:
https://mcp.endless.appThere is nothing to install and nothing to run on your machine.
Pick your client
Claude
Claude on the web, the desktop app, and Claude Code in the terminal.
Cursor and VS Code
Both read an mcp.json file — one address, four lines.
What the assistant can do
Ten tools, and all but one of them only read. Nothing in this surface creates a chat, edits an asset, generates an image or spends a credit.
Search and read assets
Search the workspace's uploads, generated images and video, documents and transcripts by title or by text inside them, then open one in full — including a recording's whole transcription.
Open a project
List the projects you can read, open one by its slug, and search assets inside that project only.
Read past chats
Find a conversation by title or by something said in it, then read its messages in order.
Choose the workspace
Confirm which account the client is signed in as, see the workspaces it belongs to, and switch between them. The one write in the catalog — it changes your selection, nothing else.
Long results are shortened, not silently cut. A list comes back ten rows at a time with a cursor for the next page, and a very long transcript or conversation ends with a note saying it was truncated.
What it can't do
It can't see more than you can
Every tool runs the same query the app runs, with the same permission checks and the same asset visibility rules. A private asset belonging to a colleague is invisible here too — being an admin does not change that.
It can't write anything
No creating, editing, deleting or generating. Ask Claude to make an image from your brand references and it will tell you it can't — that work stays in Endless, where the credits and the model catalog live.
One workspace at a time
An Endless sign-in can belong to several workspaces, and the authorization flow has no workspace picker — so the server decides which one the tools act on.
One workspace, no question
If your account belongs to exactly one workspace, that's the one. Nothing to choose.
More than one, so it asks
With two or more, the first workspace-scoped call refuses and lists your workspaces by name. Say which one you mean and the assistant switches to it.
The choice sticks
Your selection is remembered for 90 days, across clients and sessions. Ask the assistant to switch whenever you move to another workspace's work.
It never guesses. A wrong guess would mean one client's material answering a question about another, so the server would rather ask — even though the refusal costs you one extra turn.
Before you start
An Endless account
Any plan. You authorize the client against your own account, so the tools reach exactly the workspaces you're a member of.
A client that supports remote MCP
Remote means over the internet, with a sign-in — no process on your machine, which is why it also works in a browser and on a phone.
A ceiling of 60 tool calls a minute
Per account, across every client you've connected. Ordinary use never reaches it; a runaway loop does.
If something goes wrong
Start by asking who it is
"Ask Endless who I am." It answers with the account, the workspaces and which one is active — the fastest way to tell a broken sign-in from an empty workspace.
A sign-in that ends nowhere
If the browser window closes without connecting, remove the connector or server and add it again. Check the address has no trailing slash and no path after it.
No results you expected
Confirm the active workspace first, then whether the asset is private to someone else. Both look identical from the client's side.