Connect Codex to Searcherries

Connect Codex to the Searcherries remote MCP server so it can read your collected project data. You need a working Codex CLI installation and paid-plan access in Searcherries.

The same connection details are displayed under Codex on the MCP page.

Connect with browser authorization

Run this command in your terminal:

codex mcp add searcherries --url https://app.searcherries.com/mcp/searcherries

Then sign in:

codex mcp login searcherries

Complete the Searcherries authorization flow in the browser. Check that you are signed in to the account whose projects you want Codex to read.

Browser authorization does not require you to generate a personal access token or manually copy the Claude OAuth Client ID.

Verify the connection

Run:

codex mcp list

In Codex, ask:

Use Searcherries to list my projects. Ask me which project to analyze if there is more than one.

After selecting a project, you can ask for a report based on the available visibility, competitor, citation, and analytics data.

For current Codex configuration details, see the official MCP documentation.

Use a personal access token when needed

If your client cannot complete OAuth, create a token on the Searcherries MCP page. Add the following configuration to the Codex configuration file, normally ~/.codex/config.toml:

[mcp_servers.searcherries]
url = "https://app.searcherries.com/mcp/searcherries"
bearer_token_env_var = "SEARCHERRIES_MCP_TOKEN"

Provide the token through an environment variable named SEARCHERRIES_MCP_TOKEN in the environment that launches Codex. Keep the token out of shared configuration files, repositories, and screenshots.

The token guide explains creation, replacement, and revocation.

Troubleshooting

If the server cannot be found, check that the URL includes /mcp/searcherries. If authorization fails, confirm your Searcherries subscription and repeat the browser login.

For token authentication, the variable must be available to the actual Codex process, not only to a different terminal session. If a token was revoked or expired, replace it.

The connection can read saved data but cannot run a new scan or change your project. A successful connection therefore does not make an old report current by itself.