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.
Add the server to your project or user configuration. Cursor uses the mcpServers key. VS Code uses servers and requires "type": "http".
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. Complete sign-in 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"
}
}
}You can also run MCP: Add Server, 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". Use the configuration for your editor.
Example requests
Ask the assistant to find the copy, screenshots and clips saved in Endless for the page you are building.
When it doesn't work
The server never appears
Check the configuration keys against the examples above and confirm that the JSON is valid.
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.