Every Model, Every Agent, the Live Web: The You.com MCP Server Comes to Warp

‍TLDR: The You.com MCP Server (you-search, you-contents, you-research, and the optional you-finance tool) is now a drop-in addition to Warp's agent stack. Because it speaks standard MCP over Streamable HTTP, it slots into Warp Agent exactly like GitHub, Linear, or Sentry through Warp's MCP settings, a shared Warp server, or a file-based .warp/.mcp.json.

This article covers how to wire it up, which of the four tools to expose and when, and how to use Warp's Agent Profiles, Rules, and cloud agent platform to keep a terminal-based agent grounded in the live web without turning every session into an open-ended research project.

Terminal-based agents are good at taking an ambiguous instruction, breaking it into steps, and acting on the result without a human clicking through ten tabs. What they're historically bad at, however, is knowing anything that happened after their training cutoff—a new CVE, a vendor's current pricing page, a library's latest breaking change, or this morning's incident report from a status page, for example.

Warp Agents already close part of that gap with native web search for models that support it. But native web search is model-gated (only specific Claude and OpenAI releases get it), untyped (you get pages and snippets, not structured fields your agent can reason over deterministically), and single-purpose (there's no dedicated research-synthesis mode, no finance index, no batch content extraction). The You.com MCP Server is built to close that gap fully, and because it's MCP-native, it works the same way inside Warp as any other developer tool your agents already call.

What Is the You.com MCP Server?

The You.com MCP Server (io.github.youdotcom-oss/mcp in the Anthropic MCP Registry) exposes four tools over the Model Context Protocol:

It's available two ways: 

1. As a hosted remote server at https://api.you.com/mcp (Streamable HTTP, recommended—always current, no local install)
2. As a local NPM package (npx @youdotcom-oss/mcp) over STDIO for self-hosting

Both support a free tier (you-search only, 100 queries/day, no credentials) so you can test the wiring before adding a key.

Getting Started: Adding You.com to Warp

Warp reads MCP servers from three places, and the You.com server works in all three.

Option 1: Warp Settings (Fastest for One-Off Use)

Go to Settings → Agents → MCP servers → + Add, choose Streamable HTTP or SSE Server (URL), and paste:

{
 "mcpServers": {
 "ydc-server": {
 "url": "https://api.you.com/mcp",
 "headers": {
 "Authorization": "Bearer <YDC_API_KEY>"
 }
 }
 }
}

Get a key at you.com/platform. If you'd rather skip key management entirely, drop the headers block—any MCP client that implements OAuth 2.1 (Warp does) will get a 401 with a WWW-Authenticate challenge, open a browser, and complete the flow automatically. Credentials are then stored locally and reused across sessions.

One-Click Install for Your Team

Once one person on a team has the You.com server configured, nobody else on that team needs to touch a JSON block at all. From the MCP servers page, click the share icon on the ydc-server entry — Warp automatically scrubs the YDC_API_KEY value out of the Authorization header and replaces it with a variable before sharing, so no one's key travels with the config.

Teammates find it waiting under the Shared section of their own MCP settings (Warp Drive → Personal → MCP Servers → Shared). Installing from there is a single click; Warp prompts each person only for the scrubbed value — in this case, their own YDC_API_KEY — and wires up the rest of the config automatically. It's the fastest way to roll the You.com MCP server out past your own machine without asking every teammate to hand-copy a config block or manage the URL themselves.

Option 2: Local NPM package (STDIO)

For fully local development or environments without outbound HTTPS to api.you.com, add it as a CLI server instead:

{
 "mcpServers": {
 "ydc-server": {
 "command": "npx",
 "args": ["@youdotcom-oss/mcp"],
 "env": {
 "YDC_API_KEY": "<YDC_API_KEY>"
 }
 }
 }
}

Option 3: File-Based Config for Teams

If you want the same You.com server definition to follow a repo across Warp, Claude Code, and Codex—rather than living only in one person's local Warp settings—write it into .warp/.mcp.json at the project root, or ~/.warp/.mcp.json globally. 

Warp's /agent-add-mcp skill will do this for you conversationally. Tell the agent to add the You.com MCP server, choose global or project scope, and review the generated file before it's used. Project-scoped servers require an explicit one-time approval per machine, which is deliberate—Warp won't let a cloned repo silently spin up a server that calls out with an API key.

Once it's added, Warp shows you-search, you-contents, and you-research as available tools (assuming the default scope—more on you-finance below). Test it with a plain-language prompt: "Search the web for the current LTS version of Node.js and extract the release notes." Your agent will ask permission the first time, then use the tools automatically on subsequent requests, governed by whatever MCP permission level you've set (see below).

Scoping Which Tools Are Exposed

By default, the remote server surfaces you-search, you-research, and you-contents. you-finance is opt-in, and you can also narrow the default three down if a given profile only needs one capability.

On the remote server, append ?tools= with a comma-separated list:

{
 "mcpServers": {
 "ydc-server": {
 "url": "https://api.you.com/mcp?tools=you-search,you-finance",
 "headers": { "Authorization": "Bearer <YDC_API_KEY>" }
 }
 }
}

Alternatively, send X-Allowed-Tools as a header to hide specific tools from a session without changing the URL:

{
 "mcpServers": {
 "ydc-server": {
 "url": "https://api.you.com/mcp",
 "headers": {
 "Authorization": "Bearer <YDC_API_KEY>",
 "X-Allowed-Tools": "you-research,you-contents"
 }
 }
 }
}

On the local NPM package, use the YDC_ALLOWED_TOOLS environment variable instead of a query string:

{
 "env": {
 "YDC_API_KEY": "<YDC_API_KEY>",
 "YDC_ALLOWED_TOOLS": "you-search,you-finance"
 }
}

Scoping matters more in a terminal agent context than it might in a chat UI, because Warp Agent Profiles are typically task-shaped—a "Research" profile, a "Ship it" profile, an on-call profile—and each of those should see only the You.com tools relevant to its job.

Best Practices: Making This Work Well Inside Warp

Getting the server connected is the easy part. Getting an agent to use it appropriately (i.e., reaching for you-research on a genuinely ambiguous question but not burning an exhaustive research pass to check a version number) is where MCP integrations often fall short. A few patterns that hold up in practice:

1. Match tool scope to Agent Profile, not to the whole workspace. 

Warp's Agent Profiles let you run different autonomy and tool configurations side by side—a cautious profile for production work, a faster one for scratch exploration. Give a "deep research" profile the full ?tools=you-search,you-research,you-contents,you-finance set with you-research effort left to the model's judgment, and give a "quick lookup" profile only ?tools=you-search so it can't accidentally kick off a multi-minute synthesis pass when a single search would do.

2. Use MCP permissions to set the trust level per profile, not per call. 

Under Settings → Agents → Profiles → Permissions → MCP permissions, you can allowlist the You.com server (act without asking) in profiles where you fully trust the workflow, and require confirmation in profiles that touch anything customer-facing or cost-sensitive. you-finance and you-research at deep/exhaustive effort are the ones worth gating, since they're the most expensive calls.

3. rite a Rule that tells the agent when You.com is the right tool, not just that it exists. 

An AGENTS.md entry like "For questions about current library versions, CVEs, or anything time-sensitive, use the you-search MCP tool rather than answering from memory. For multi-source synthesis (competitive comparisons, market questions, 'what's the current best practice for X'), use you-research at standard effort unless the task explicitly calls for exhaustive. Use you-finance only for filings, earnings, or market-data questions." removes the guesswork and keeps effort levels—and therefore cost—intentional rather than default-to-maximum.

4. Extend the same server to unattended Oz cloud agents.

Local MCP config only covers interactive sessions. For scheduled or unattended work—like a nightly dependency-freshness check, or a competitor-pricing watch that posts to Slack, for example—pass the You.com server to a cloud run explicitly:

oz mcp list
oz agent run-cloud --mcp "<YDC_MCP_SERVER_UUID>" \
 --prompt "Check for any breaking changes announced this week for our top 5
pinned dependencies and summarize."

Store the YDC_API_KEY as an Agent Secret rather than inline in the config—cloud runs execute away from your desktop, so nothing should depend on a value that only exists in your local shell.

5. Treat the API key like any other credential in the security checklist.

Warp's own MCP guidance is blunt about this and it applies directly here. Use the narrowest key scope the workflow needs, prefer OAuth over a hardcoded key for interactive local use, review any project-scoped .warp/.mcp.json before approving it (especially if it was generated by an agent you didn't personally review), and remember that MCP logs can contain full response bodies—scrub before sharing a log with a teammate or in a bug report.

Example Workflows

A few concrete shapes this takes once it's wired up:

• Pre-upgrade dependency check. Before bumping a major version in a terminal session, ask the agent to run you-search scoped to the package's changelog domain and you-contents to pull the actual release notes, rather than trusting the model's memory of what changed.
• Incident context while debugging. Mid-debugging session, ask the agent to check you-search for whether an error signature matches a known open issue or recent outage, without leaving the terminal to open a browser tab.
• Due diligence before a build decision. you-research at deep effort to compare two libraries or infra approaches with citations, so the write-up in your PR description or ADR has sources attached rather than "the agent said so."
• Scheduled competitive or market monitoring. An Oz cloud agent running weekly, combining you-search (or you-finance for public companies) with a Slack MCP server to post a digest—the same shape as the You.com + One competitive intelligence loop, just orchestrated through Warp's Oz scheduling instead of a standalone cron job.

Get Started

1. Get a key at you.com/platform, or skip this step and use OAuth / the free tier.
2. In Warp, go to Settings → Agents → MCP servers → + Add, and paste the remote server config above (or run /agent-add-mcp and describe what you want).
3. Scope the tool set to the profile: default (you-search, you-research, you-contents) for most work, add ?tools=...,you-finance for anything finance-adjacent.
4. Set MCP permissions per Agent Profile, and add a Rule to AGENTS.md so the agent knows when to reach for each tool.
5. For unattended workflows, share the server from Warp Drive and reference it by UUID in an Oz cloud run.

Full API and MCP documentation is at you.com/docs/build-with-agents/mcp-server. For enterprise rate limits or a dedicated you-finance allocation, contact the You.com team directly.