Choose an MCP connection
Remote MCP does not require the local MCP package. Installing CLI does not register a native MCP server. Installing a skill does not sign in or connect tools.
Choose a dedicated guide
Use the separate pages for Claude, Codex, Claude Code, ChatGPT, Cursor, OpenClaw, and Hermes. This page covers generic remote MCP and local stdio connections for additional clients.Separate CLI guides for terminal agents
For terminals, scripts, Gemini CLI, OpenCode, and GitHub Copilot CLI, follow EvoLink CLI setup for installation, sign-in, skill targets, and free verification. Agents that execute commands can use CLI; configure native MCP with the remote or local instructions below.Linux and SSH sign-in
When CLI runs remotely but your browser is local, follow SSH callback forwarding after meeting Linux secure credential storage requirements. Remote MCP callbacks are managed by the host and do not use the CLI forwarding steps.Local stdio MCP with an API Key
A stdio-only client can launch a local MCP process. It needs Node.js 18+ and a personal API Key, rather than remote MCP browser OAuth.1
Prepare Node and a dedicated Key
EVOLINK_API_KEY through the client’s safe environment or secret settings, not agent chat, shared screenshots, or a repository.2
Configure the local launcher
Choose local/stdio in the client’s MCP settings:On first launch, npx retrieves the package. The host communicates over stdio and the local process calls the platform API. Ensure the host can find npx; a GUI application may have a different environment from your terminal.
YOUR_API_KEY below is a placeholder for private local configuration. Prefer environment inheritance when supported.3
Allow directories when local files are needed
For local-path uploads, set
EVOLINK_UPLOAD_ALLOWED_DIRS to allowed absolute directories in the process environment. Separate multiple directories with : on macOS/Linux or ; on Windows. Local-path uploads are disabled without this setting. Remote MCP never accepts file_path.This controls local file access, not model format, duration, or size limits. URL/base64 usage does not need local directory access.4
Reload and verify free tools
Save configuration, enable EvoLink, and reload or open a new session as your host requires. Ask it to call
check_balance and search_models and confirm real results. Starting a process or listing tools alone is not successful account verification.Local stdio does not provide remote single-use upload tools prepare_upload / get_upload. Inspect actual tools/list. The personal Key has its own limits, not OAuth Key limits.Claude Code and Codex configuration
With the Key already provided through the safe environment, Claude Code can register using this command instead of the JSON example:@latest does not replace an already running process. See central troubleshooting for startup, Key, and local-path failures.
Other remote MCP clients
The client needs Streamable HTTP, OAuth, and browser callbacks. A client limited to static Keys or stdio should use local MCP above.1
Add the server
Create an MCP connection named EvoLink with Streamable HTTP and this URL:Do not enter a documentation URL, platform
/v1 URL, or npx command.2
Complete OAuth and enable tools
Choose OAuth, use the client’s sign-in action, approve in the browser, and return. Confirm the connection and tools are enabled. A static API Key is not this connection’s OAuth token.
3
Verify for free