Connect ClipSeek to Codex

You need two things from ClipSeek → Settings → AI Agent: the connection URL and the access token. Keep ClipSeek running throughout setup and use.

1. Prepare ClipSeek

1. Open a library and turn on Enable agent access.
2. Keep the listening scope at This computer only when Codex runs on this computer.
3. Copy the displayed local URL, then select Copy access token.

Leave Allow organization and imports off for your first test. Searching, reading subtitles, and previewing do not need it.

2. Add the server in Codex

1. Open Settings → MCP servers → Add server.
2. Set the name to clipseek and choose Streamable HTTP.
3. Enter the URL copied from ClipSeek.
4. If your version has a Bearer Token field, paste the access token there. If it does not, use the configuration example below.
5. Save and restart when prompted. Type /mcp in the composer to check the connection.

Codex interface labels may vary by version. The official OpenAI MCP guide covers desktop, CLI, and IDE configuration.

Advanced: configure config.toml

Add the following to your local ~/.codex/config.toml. Replace the URL with the exact address shown in ClipSeek; <port> is a placeholder.

[mcp_servers.clipseek]
url = "http://127.0.0.1:<port>/mcp"
bearer_token_env_var = "CLIPSEEK_MCP_TOKEN"
default_tools_approval_mode = "prompt"
tool_timeout_sec = 120

Set the local environment variable CLIPSEEK_MCP_TOKEN to the copied token in the environment that launches Codex, then fully restart Codex. The configuration contains the variable name, not the token itself. Setting it in an unrelated terminal does not update an already-running desktop app.

prompt requests approval for tools from this server. Codex also supports writes, which prompts for tools not marked read-only. This client policy is separate from ClipSeek's organization/import permission.

Avoid duplicate [mcp_servers.clipseek] sections. Keep credentials out of project files and shared configuration.

3. Test without changes

Send this request in Codex:

List my ClipSeek libraries and tell me which one is currently open. Do not change anything.

If you get the library list, try a prompt from Common workflows.

If the connection fails

What you see	What to check
Cannot connect or connection refused	ClipSeek is running, Agent access is enabled, and its status says Running. Copy the URL again.
Unauthorized / HTTP 401	Copy the current token again. A regenerated token invalidates the old one. For environment-variable setup, restart Codex with the updated variable.
Service stopped or port error	Read the error in ClipSeek's AI Agent settings. A previously saved port may be occupied; the service does not silently choose a different one.
Library unavailable	Open the target library, or ask Codex to list libraries before choosing one.
Organization or import rejected	Enable Allow organization and imports only when you need those actions.

Only share screenshots after hiding tokens and full download links. See Security and permissions.