Cursor and VS Code
Both editors read a small mcp.json file. Add the Endless address to it, sign in once, and your workspace is available to the assistant beside your code.
Both editors configure an MCP server the same way: a few lines of JSON, either in the project or in your own profile. The key names differ, and that's the only difference worth knowing.
https://mcp.endless.appCursor
Create the file
.cursor/mcp.json in the project root, or ~/.cursor/mcp.json to have it in every project.
{
"mcpServers": {
"endless": {
"url": "https://mcp.endless.app"
}
}
}Sign in
Cursor picks the file up and offers the sign-in — approve it in the browser window that opens. The server also appears under Customize in the sidebar, where you can connect, disconnect or switch it off.
Check it
Ask the assistant: "Ask Endless who I am."
No headers and no auth block. Endless authorizes with your Endless account
through the sign-in flow, so there is no token to paste and nothing secret in
the file.
VS Code
Create the file
.vscode/mcp.json in the workspace, or run MCP: Open User Configuration from the command
palette to keep it to yourself.
{
"servers": {
"endless": {
"type": "http",
"url": "https://mcp.endless.app"
}
}
}MCP: Add Server walks you through the same thing if you'd rather not write the file — choose
an HTTP server and paste the address.
Sign in
Start the server from the file's own Start action, or from the MCP view. The sign-in opens in your browser and returns you to the editor.
Check it
Ask the assistant: "Ask Endless who I am."
servers in VS Code, mcpServers in Cursor, and VS Code wants "type": "http". Copying one file into the other editor fails quietly — the server
simply never appears.
Why this is useful next to code
The copy, screenshots and clips for a landing page are already in Endless. Ask the assistant to search the workspace for them instead of pasting them in one by one, and the alt text it writes describes the real image.
When it doesn't work
The server never appears
Check the key name against the table above, then that the JSON parses. Both editors ignore a malformed file rather than reporting it.
The sign-in doesn't come back
Remove the entry, restart the editor, and add it again. Check the address has no trailing slash.
It can't tell which workspace
Expected on an account in more than one. The refusal lists them; name one and it's remembered for 90 days, across every client.
Nothing comes back
Confirm the active workspace, then whether the asset is private to a colleague — see assets and visibility.
A committed .cursor/mcp.json or .vscode/mcp.json holds an address and no
credential, so it's safe to share with the repository. Every teammate still
signs in as themselves and reads only what their own account can read.