MCP Server

The override contract is broadcast on the tool entry itself. A tools/list response returns the accepted fields and their constraints in tool._meta["com.you.com/search"]:

{
  "name": "you-search",
  "_meta": {
    "com.you.com/search": {
      "description": "Host-supplied search overrides. Send an object under the com.you.com/search key in tools/call params._meta (or X-Search-* HTTP headers); every field is optional and wins over model-supplied arguments. Host-only fields (language, country, include_domains, boost_domains) are settable here and never by the model.",
      "schema": {
        "type": "object",
        "properties": {
          "count": { "type": "integer", "minimum": 1, "maximum": 100 },
          "country": { "type": "string", "enum": ["AR", "AU", "AT", "...", "US"] },
          "safesearch": { "type": "string", "enum": ["off", "moderate", "strict"] }
        }
      }
    }
  }
}

Because tools/list results are cacheable, you can fetch the contract once and reuse it to validate overrides at runtime.

Every override field has an HTTP header equivalent, sent alongside your other request headers:

For setup, follow the MCP installation guide.

Quick setup (API key):

claude mcp add --transport http ydc-server https://api.you.com/mcp --header "Authorization: Bearer <YDC_API_KEY>"

OAuth 2.1 (no API key): Connect without credentials and Claude Code will initiate the OAuth flow automatically:

claude mcp add --transport http ydc-server https://api.you.com/mcp

For setup, follow the MCP installation guide.

Local config lives in claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Paste the local NPM package template from Getting Started, then restart Claude Desktop. For setup, follow the MCP installation guide.

Config file: ~/.cursor/mcp.json. For setup, follow the MCP installation guide. Omit the type field. To run free, discover, a mixed allowlist, research, and finance as separate entries, paste the multiple You.com entries block. Keyed entries need Authorization: Bearer <YDC_API_KEY> or OAuth. ?profile=free and ?profile=discover stay keyless.

Quick setup (command line):

code --add-mcp '{"name":"ydc-server","url":"https://api.you.com/mcp","type":"http","headers":{"Authorization":"Bearer <YDC_API_KEY>"}}'

For setup, follow the MCP installation guide. Use the configuration template above.

For setup, follow the MCP installation guide. Use the configuration template above.

Supported IDEs: IntelliJ IDEA, PyCharm, WebStorm, GoLand, RubyMine, PhpStorm, and more (requires AI Assistant enabled)

For setup, follow the MCP installation guide. Use the configuration template above without the type field.

Quick setup (OAuth, no API key):

droid mcp add you https://api.you.com/mcp --type http

Droid initiates the OAuth 2.1 flow automatically. Run /mcp inside a Droid session to complete the browser sign-in.

API key with env injection (recommended for secrets):

droid mcp add you https://api.you.com/mcp --type http \
  --header 'Authorization: Bearer ${YDC_API_KEY}' --no-oauth

Droid expands ${YDC_API_KEY} at connection time, so the key stays out of the config file. Add --no-oauth to prevent Droid from attempting OAuth alongside the header.

Hardcoded API key:

droid mcp add you https://api.you.com/mcp --type http \
  --header 'Authorization: Bearer <YDC_API_KEY>' --no-oauth

Free profile (no account):

droid mcp add you https://api.you.com/mcp?profile=free --type http --no-oauth

Verify: droid mcp list or /mcp inside a Droid session.

For setup, follow the Factory MCP guide.

Codex:

For setup, follow the MCP installation guide.

opencode:

For setup, follow the MCP installation guide. Use the remote server template in Getting Started.

LM Studio:

For setup, follow the MCP installation guide. Use the remote server template in Getting Started, without the type field.

Gemini CLI:

Follow the MCP server setup guide using the standard configuration template.

Symptoms: Authentication errors, “Invalid API key” messages

Solutions:

1. Verify your API key is active at you.com/platform
2. Check for extra spaces or quotes in your configuration
3. Ensure the API key has the correct scopes enabled
4. For the local NPM package, verify the YDC_API_KEY environment variable is properly exported
5. On the remote server, try OAuth 2.1, described in Authentication

Symptoms: Browser window doesn’t open, OAuth flow fails, “Invalid token” errors

Solutions:

1. Confirm your MCP client supports OAuth 2.1—check your client’s documentation
2. If the browser window opens but authorization fails, try signing in to you.com first in the same browser
3. If the flow completes but the client still receives 401, restart the MCP client to clear cached token state
4. As a fallback, use an API key from you.com/platform instead

Symptoms: “Connection refused”, timeout errors

Solutions:

1. Remote server: Check your internet connection and firewall settings
2. Local package: Ensure npx and Node.js are installed and in your PATH
3. Confirm the URL is https://api.you.com/mcp, /mcp/research, or /mcp/finance
4. Check your MCP client logs for detailed error messages

Symptoms: MCP server not appearing in IDE, tools not available

Solutions:

1. Restart your IDE after configuration changes
2. Check the IDE’s MCP logs for error messages (Claude Code: terminal output, Claude Desktop: application menu, Cursor: MCP server logs in settings, VS Code: output panel)
3. Verify the configuration file is in the correct location
4. For STDIO transport, ensure the command is executable
5. Try the remote server option if local installation fails

Symptoms: The server connects but tools/list is empty

Cause: The profile ceiling ∩ allowed-tools intersection is empty. Common cases: POST /mcp/finance?profile=free, POST /mcp/research?profile=discover, or an allowlist that names only tools the profile forbids.

Solutions:

1. Drop ?profile= (or use a profile whose ceiling includes the tool)
2. On /mcp/finance and /mcp/research, the path already forces the allowlist. A free or discover profile on that URL empties the list
3. Check X-Allowed-Tools and ?tools= for a non-empty header that replaced the query string