Skip to main content
This page covers native MCP in Claude Code. 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 HTTP server

In a terminal with Claude Code installed, run:
--scope user makes this connection available across projects for the current user. Adding it only confirms the configuration was written.
2

Sign in within Claude Code

In the Claude Code conversation, enter the following session command and select EvoLink’s authentication action:
Complete browser sign-in and approval, then check the connection in Claude Code. This session command is not a normal shell command.
3

Check tools and verify for free

Approve a pending project connection within Claude Code if prompted. In a new session, send the verification prompt below and confirm real balance and models.
For project configuration, merge into .mcp.json:
Do not put this block into .claude/settings.local.json; the command above manages user scope. See Claude Code documentation. 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.