MCP
Connect an MCP client
Choose a client and connect it to the Yep search tool with OAuth.
Server endpoint
Yep exposes one remote Streamable HTTP MCP endpoint.
https://yep.com/api/v1/mcp Authentication
The server uses OAuth only. Request search:read for search tools. Model, query-builder, and agent tools require both search:read and agent:run. Your client opens the authorization flow and stores the resulting credentials.
Set up BYOK agent tools
Call list_models to choose an allowlisted provider and model. Store the provider key in Yep at the returned setup_url; provider-key plaintext is never accepted by an MCP tool. If setup is missing, the tool returns provider_key_missing with the same setup URL in structuredContent.
Recover from tool errors
Tool execution failures set isError to true. When error.validation is present, correct every RFC 6901 issue before retrying and do not repeat unchanged input.
{
"error": {
"code": "invalid_request",
"reason": "malformed_request",
"message": "invalid request: request body violates the public contract",
"recovery": null,
"agent_session_id": null,
"validation": {
"contract": "SearchPostRequest",
"issues": [
{
"code": "required",
"path": "/query",
"suggestion": "Add the required `query` field."
}
],
"truncated": false
}
},
"request_id": "00000000-0000-0000-0000-000000000000"
} Choose a client
Add the server to your user or trusted-project config, then start the OAuth flow.
[mcp_servers.yep]
url = "https://yep.com/api/v1/mcp"
auth = "oauth" Authenticate
Start the OAuth flow from the client, then approve access in the browser.
codex mcp login yep Verify the connection
Ask the client to search the web. The client should discover the search tool and open OAuth if authorization is still required.