> ## Documentation Index
> Fetch the complete documentation index at: https://evolink.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Code MCP setup

> Native remote MCP configuration, browser authorization, tool verification, and troubleshooting

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](/docs/en/cli/claude-code).

## Connect remote MCP

For native tools, use **Streamable HTTP + OAuth** with this server URL:

```text theme={null}
https://mcp.evolink.ai/mcp
```

CLI installation is not required. Back up existing configuration, merge only EvoLink, and preserve other services. Choose command-based or manual registration.

<Steps>
  <Step title="Add the HTTP server">
    In a terminal with Claude Code installed, run:

    ```bash theme={null}
    claude mcp add --transport http --scope user evolink https://mcp.evolink.ai/mcp
    ```

    `--scope user` makes this connection available across projects for the current user. Adding it only confirms the configuration was written.
  </Step>

  <Step title="Sign in within Claude Code">
    In the Claude Code conversation, enter the following session command and select EvoLink’s authentication action:

    ```text theme={null}
    /mcp
    ```

    Complete browser sign-in and approval, then check the connection in Claude Code. This session command is not a normal shell command.
  </Step>

  <Step title="Check tools and verify for free">
    ```bash theme={null}
    claude mcp list
    ```

    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.
  </Step>
</Steps>

For project configuration, merge into `.mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "evolink": {
      "type": "http",
      "url": "https://mcp.evolink.ai/mcp"
    }
  }
}
```

Do not put this block into `.claude/settings.local.json`; the command above manages user scope. See [Claude Code documentation](https://code.claude.com/docs/en/mcp).

After authorization, send this in the agent chat:

```text theme={null}
Use EvoLink to check my account balance and search available image models. Do not generate anything yet.
```

**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.

| Symptom | Action |
| - | - |
| URL added but no tools | Enable the connection, complete authorization, refresh, and check organization policy |
| 401 or authentication required | Reauthorize this MCP connection and retain original task IDs |
| 403 or tool denied | Check host permissions, account/Key status, and network errors |
| Timeout or lost response | Query and recover the original operation instead of regenerating |
| Link-only or gray preview | Open and deliver the original without automatically remaking it |

See [MCP costs, access, and troubleshooting](/docs/en/mcp/billing#faq). Read the [creation workflow](/docs/en/mcp/overview#workflows) before submitting; call shapes are in the [MCP tool reference](/docs/en/mcp/tools).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.