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

# ChatGPT & Codex Plugin

> ChatGPT custom MCP, Codex and Claude Code repository plugins, and standalone skill installation

Plugins can package remote MCP configuration with agent guidance. Each host uses its own installation and authorization mechanism.

| Entry | Installed content | Media execution |
| - | - | - |
| ChatGPT custom MCP plugin | A server connection created in ChatGPT | ChatGPT calls remote MCP |
| Codex repository plugin | EvoLink remote MCP configuration and evolink-mcp skill | Codex calls remote MCP |
| Claude Code repository plugin | EvoLink remote MCP configuration and evolink-mcp skill | Claude Code calls remote MCP |
| CLI bundled skill | evolink-cli instructions and references | The agent runs CLI, which calls the API directly |
| Standalone evolink-mcp skill | MCP invocation guidance only | MCP configuration and authorization are still required |

## ChatGPT custom MCP plugin

Follow [ChatGPT setup](/docs/en/mcp/chatgpt) to add a custom MCP server:

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

Choose OAuth, approve browser login, then enable EvoLink in your conversation. ChatGPT does not use the Codex marketplace commands below or require a local npm CLI installation.

A custom connection does not mean EvoLink is listed in the public plugin directory. Creation and generation-tool access depend on your account, host version, and workspace permissions. See [OpenAI custom MCP guidance](https://developers.openai.com/api/docs/guides/custom-mcp-server).

## Codex repository plugin

Confirm that your Codex version supports `plugin`. This plugin uses native remote MCP; the website’s CLI prompt is another method. CLI users do not also need a plugin for generation.

<Steps>
  <Step title="Add the source and install the plugin">
    Run in the machine and user terminal that runs Codex:

    ```bash theme={null}
    codex plugin marketplace add Evolink-AI/mcp-plugin
    codex plugin add evolink@evolink
    codex plugin list --json
    ```

    Confirm EvoLink appears in the plugin list. It provides remote MCP configuration and the `evolink-mcp` skill, not the EvoLink CLI.
  </Step>

  <Step title="Load the plugin and authorize">
    Refresh plugins or open a new Codex conversation and confirm the EvoLink server is loaded. Complete the host’s browser OAuth when prompted. With the server registered and this command supported, use:

    ```bash theme={null}
    codex mcp login evolink
    ```

    Keep it running through sign-in and approval, then return to Codex. Choose a single registration source when manual MCP configuration already exists.
  </Step>

  <Step title="Verify tools and the skill">
    ```text theme={null}
    Confirm you have read evolink-mcp, then use EvoLink to check balance and available image models. Do not generate anything yet.
    ```

    Success means the skill was read and actual `check_balance` and `search_models` calls succeeded; a plugin list alone does not verify authorization.
  </Step>
</Steps>

To update the source, run this and refresh the plugin in the host, checking its actual version:

```bash theme={null}
codex plugin marketplace upgrade evolink
```

See [Codex CLI reference](https://learn.chatgpt.com/docs/cli/reference) and [Codex setup](/docs/en/mcp/codex) for manual MCP setup; find CLI instructions in the [separate CLI guide](/docs/en/cli/codex).

## Claude Code repository plugin

Use a plugin-capable Claude Code version. These are **Claude Code conversation commands**, not normal shell commands.

<Steps>
  <Step title="Install the repository plugin">
    ```text theme={null}
    /plugin marketplace add Evolink-AI/mcp-plugin
    /plugin install evolink@evolink
    ```

    Wait for installation and confirm EvoLink is enabled for the current user/project. Preserve other plugins.
  </Step>

  <Step title="Authorize remote MCP">
    ```text theme={null}
    /mcp
    ```

    After refreshing the plugin, select EvoLink and complete browser authentication. Avoid a duplicate manually registered connection.
  </Step>

  <Step title="Verify for free">
    Ask the assistant to confirm reading `evolink-mcp` and actually query balance and models without generation. See [Claude Code setup](/docs/en/mcp/claude-code) for manual MCP setup; find CLI instructions in the [separate CLI guide](/docs/en/cli/claude-code).
  </Step>
</Steps>

## Install only the MCP skill

If native MCP is already configured and you only need agent guidance:

```bash theme={null}
npx skills add Evolink-AI/mcp-plugin -g -y
```

This retrieves repository skills through the skills installer. It does not install EvoLink CLI, start local MCP, or complete OAuth. Verify the host discovers the destination and reads evolink-mcp.

## What the plugin teaches

The source is [Evolink-AI/mcp-plugin](https://github.com/Evolink-AI/mcp-plugin). Configuration points to hosted remote MCP. Its skill covers model discovery, parameter validation, estimates and approval, reference uploads, generation, tasks, failure recovery, and original delivery. It does not add code development, arbitrary file editing, or full video editing to EvoLink MCP tools.

CLI and MCP skills can share media policies, but use different commands and tools. Choose one path per task. If submission times out with an unknown outcome, recover the original request or task\_id instead of regenerating through another entry. See [agent resources](/docs/en/cli-mcp/agent-resources#skills) for contents and directories and [platform reference](/docs/en/mcp/tools) for parameters.

See [costs and retention](/docs/en/mcp/billing) for limits and revocation. Plugin installation, skill installation, and OAuth authorization do not approve a paid generation request.

## Plugin installation problems

| Symptom | Next step |
| - | - |
| Missing plugin / marketplace commands | Check host version and official setup, or use its manual MCP guide or the [separate CLI setup](/docs/en/cli/setup) |
| Cannot retrieve the repository | Check GitHub connectivity and host source settings; keep the original error |
| Installed but tools are missing | Refresh the actual session, enable the plugin, and complete OAuth |
| Duplicate server or skill | Back up configuration, inspect sources, keep the intended one, and preserve other services |
| Tools list but calls fail | Verify authorization with free balance queries; see [MCP troubleshooting](/docs/en/mcp/billing#mcp-connection) |

Plugin installation does not approve paid tests. See [central troubleshooting](/docs/en/mcp/billing#faq) for discovery and other problems.


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