Skip to main content
This page covers native MCP in Cursor. The remote service uses Streamable HTTP and browser OAuth without requiring EvoLink CLI. For command and skill execution, use the separate CLI guide.

​
Connect remote MCP

For native tools, use Streamable HTTP + OAuth with this server URL:
CLI installation is not required. Back up existing configuration, merge only EvoLink, and preserve other services. Choose command-based or manual registration.
1

Add the server to Cursor

Choose Add to Cursor, allow the browser to open Cursor, review the name and URL, and confirm. Use manual configuration below if the application does not open.
2

Enable and authorize the connection

Open Cursor’s MCP settings, enable EvoLink, and follow browser sign-in and approval. Return to Cursor and inspect its connection and tool list.
3

Verify for free in Agent

Open an Agent conversation with tool permission and send the verification prompt below. Refresh the connection or start a new conversation if tools are missing; check whether project configuration overrides or disables the global entry.
Manual configuration uses ~/.cursor/mcp.json globally or .cursor/mcp.json for one project. Merge into the existing mcpServers object:
See Cursor configuration. After authorization, send this in the agent chat:
Success: actual check_balance and search_models calls return results. Verify these tools in the actual MCP connection.

​
Updates, disconnection, and troubleshooting

EvoLink updates the hosted MCP server. Refresh the actual client session after configuration changes. Reauthorize through that client’s OAuth action when needed. Disable, sign out, or remove EvoLink in host MCP settings to disconnect; retain other servers. See MCP costs, access, and troubleshooting. Read the creation workflow before submitting; call shapes are in the MCP tool reference.