Before you begin
Have EvoLink and Claude accounts, plus a client version, plan, and workspace permission that allows custom MCP. If the add action is unavailable, check host access first rather than running terminal instructions in chat.Connect EvoLink step by step
1
Open the connector action
Choose Add to Claude. It matches the website and prefills the name and URL. If it does not open, add a custom connector in Claude’s Connectors settings.
2
Review the URL and add the connector
Name it EvoLink and use this remote server URL:Use a Streamable HTTP remote connection with OAuth/browser sign-in. Do not enter a documentation or REST URL. Confirm EvoLink appears in the saved list.
3
Sign in and approve in the browser
Choose Connect/Authenticate, sign in to EvoLink, review the account and permissions, approve, and return to Claude. Use the current sign-in action if a window does not open; start a new attempt when the old link expires.
4
Enable it in a conversation and verify
Enable EvoLink in the conversation’s connector/tool selection, then send the prompt below. Saving a connector alone does not enable it in the current chat.Success: actual balance and model results. Claude Code is a separate terminal client; use its setup page.
Free verification and the first media task
Once connected, send this in a conversation with EvoLink enabled:check_balance and search_models calls. Sign-in and these queries do not create paid media tasks. For generation, describe content and specifications, review the proposed model, parameters, and estimate, then explicitly approve submission. See the first media workflow.
Use publicly accessible reference links supported by the model. A chat attachment may not expose original file bytes to MCP, and the remote service cannot read your computer’s paths. See references and uploads.