Add the Yep MCP server to your client, then sign in with your Yep account in the browser. You do not need an API key, and there is nothing to install.
Choose your agent Codex Add the server to your Codex configuration, then start the OAuth flow.
Configuration location ~/.codex/config.toml
[mcp_servers.yep]
url = "https://platform.yep.com/api/v1/mcp" Sign in Start the sign-in from the client, then approve access in the browser.
Verify the connection Ask Codex to search the web with Yep. Without a local browser, run codex mcp login yep --no-browser and open the printed URL elsewhere.
Claude Code Add the remote HTTP server at user scope, then sign in from the command line. Run claude mcp add with --scope project instead to share the server through the project's .mcp.json.
Configuration location ~/.claude.json
claude mcp add --transport http yep --scope user https://platform.yep.com/api/v1/mcp
claude mcp login yep Verify the connection Start a new session and ask Claude Code to search the web with Yep. Run /mcp in the session to see the server's status and sign in again.
Claude Desktop Open Customize, then Connectors, and choose Add custom connector. Enter the MCP URL, and under the OAuth client setting choose Register automatically. On a Team or Enterprise plan, an Owner adds the connector under Organization settings, and members then connect it.
Configuration location Customize > Connectors
https://platform.yep.com/api/v1/mcp Verify the connection Select Connect on the connector and approve access in the browser. Then turn the connector on in a chat and ask Claude to search the web with Yep.
Cursor Add the remote server to the global configuration, or to .cursor/mcp.json in a project, then connect it from the MCP settings.
Configuration location ~/.cursor/mcp.json
{
"mcpServers" : {
"yep" : {
"url" : "https://platform.yep.com/api/v1/mcp"
}
}
} Verify the connection Approve the sign-in when Cursor asks, then ask the agent to search the web with Yep.
VS Code Add the remote HTTP server to the workspace configuration, or run MCP: Open User Configuration to add it to your profile.
Configuration location .vscode/mcp.json
{
"servers" : {
"yep" : {
"type" : "http" ,
"url" : "https://platform.yep.com/api/v1/mcp"
}
}
} Verify the connection In a chat session, ask the agent to use the Yep server to search the web. Approve the sign-in and tool requests, then expand the tool call to confirm that it came from Yep.
Gemini CLI Add the remote HTTP server from the command line. Gemini CLI registers itself with Yep and opens the browser to sign in on the first connection.
Configuration location ~/.gemini/settings.json
gemini mcp add --transport http --scope user yep https://platform.yep.com/api/v1/mcp Verify the connection Start Gemini CLI and ask it to search the web with Yep. Run /mcp auth yep to sign in again when a token expires.
Other clients Any client that supports remote Streamable HTTP servers and OAuth sign-in can connect. Many clients accept this shape; check the field names in your client's documentation.
{
"mcpServers" : {
"yep" : {
"url" : "https://platform.yep.com/api/v1/mcp"
}
}
} Verify the connection Ask the agent to search the web with Yep. The client should list the Yep tools and open the sign-in flow when it first needs access.
Ask your agent to search the web with Yep. For the tools and their inputs, see MCP server
Troubleshooting The client does not open a sign-in page Most clients open it on their own when they first connect. If yours does not, start the sign-in from the client: claude mcp login yep in Claude Code, codex mcp login yep in Codex, or /mcp auth yep in Gemini CLI.
The server rejects my API key The MCP server signs you in with OAuth. Remove the Authorization header or API key from the client configuration, then sign in. API keys are for the REST API.
The connection fails during initialization The client must support remote Streamable HTTP servers and MCP protocol version 2026-07-28. Update the client to a version that does.
Questions Can an unattended workload use MCP? No. Signing in needs a person to approve access in the browser. For an automated workload, call the REST API with a service account.