Skip to main content
This page covers native MCP in OpenClaw. 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

Check remote MCP support

The actual Gateway version needs Streamable HTTP and OAuth support. If these commands are absent, follow that version’s upgrade guidance or use the separate CLI guide; do not invent flags for an older host.
2

Add the server and set OAuth

In the Gateway’s ~/.openclaw/openclaw.json or actual configuration, set auth to "oauth" within mcp.servers.evolink, preserving other generated fields. Supported Control UI versions can add and enable it under Settings → MCP.
3

Authorize, probe, and query

After browser approval, use the agent owned by the actual Gateway to send the prompt below. Refresh the Gateway that owns the connection when changes are not reflected; refreshing a laptop terminal does not refresh a remote Gateway.
OpenClaw’s tool policy also controls availability. See OpenClaw documentation for version, authorization, and connection ownership. 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.