Build With Agents
Agents can use our APIs via the You.com MCP server, read these docs via the Docs MCP server, and execute Skills to steer their behavior. You can set this up in a single prompt.
Onboard your agent
Which Docs to Fetch
How to Connect
Which Capability
Each API fits a different job. Choose the Right API compares latency and price.
Install From This Host
To install both MCP servers without the onboarding skill, run this prompt in your agent.
Install the You.com MCP servers
Install the You.com MCP servers so that you, the coding agent I’m currently talking to, can call them.
Product MCP, live APIs, no API key:
* Server URL: `https://api.you.com/mcp?profile=free`
* Transport: streamable HTTP
* Auth: none. This profile exposes you-search (100 queries per day) and you-discover. Do not add an API key unless I ask. User can authenticate via bearer token or OAuth.
Docs MCP. Search these docs. Fully free to use:
* Server URL: `https://you.com/docs/_mcp/server`
* Transport: streamable HTTP
* Auth: none. The tool is searchDocs.
First, identify which client you are running inside: Claude Code, Cursor, Codex, VS Code Copilot, or Windsurf. That host is the one to configure. Add both servers with the mechanism that the host expects. Do not write the config into a different client’s file.
Tell me whether this host needs a restart. Then confirm both servers connect and list the tools they expose.Docs MCP vs Product MCP
Use Docs MCP to read and search this documentation site. Use Product MCP to call the APIs.
TypeScript and JavaScript have three paths. Use fetch against the REST APIs when the application needs the JSON. Use @youdotcom-oss/mcp, or the hosted server at https://api.you.com/mcp, when an agent should call the tools. Use the Python SDK when you want a typed client that tracks new API fields. The @youdotcom-oss/sdk package is deprecated.