The You.com DX Toolkit provides an MCP server as part of a monorepo that exposes AI-powered capabilities such as real-time web search, AI-assisted answers, and content extraction. The MCP server is designed to be run in two modes: a development/STDIO mode and an HTTP mode. Use the STDIO variant when you want to interact with the server directly within scripts or CI workflows, and use the HTTP variant when you want to expose the MCP server as a network service for clients to query over HTTP. The repository includes a single MCP server package that coordinates multiple sub-packages and utilities to deliver agentic workflows across You.com's AI capabilities.

To run, you can start the MCP server in development/STDIO mode or in HTTP mode. In STDIO mode you typically interact with the server through standard input/output streams suitable for integration tests or local tooling. In HTTP mode the server exposes endpoints for clients to request web search results, AI-generated answers, and content extraction. The toolkit also provides commands for building, testing, and quality checks which you can run at the workspace or package level to ensure consistency across all packages.

Key capabilities you can rely on include: real-time web search integration, AI-driven answer generation leveraging You.com's AI capabilities, and content extraction workflows that feed contexts into agents. The MCP server is designed to be used alongside the API package and the AI SDK plugin for a complete agent-enabled development experience.

Prerequisites

• Git is installed and configured
• Bun (version >= 1.2.21) is installed for workspace management and building
• Node.js is not strictly required if you rely on Bun, but having it available is fine for compatibility
• Access to the You.com DX Toolkit repository (clone from GitHub)

Installation steps

1. Clone the repository git clone git@github.com:youdotcom-oss/dx-toolkit.git cd dx-toolkit

2. Install dependencies (workspace with Bun) bun install

3. Install or verify prerequisites for the MCP server package

   • Ensure your environment has any required environment variables (see .env.example in the repo) and copy them if needed: cp .env.example .env

     Edit .env to include necessary keys (e.g., YDC_API_KEY or others as documented)

4. Build the monorepo (optional but recommended before running tests or servers) bun run build

5. Run the MCP server (choose mode)

   • Development/STDIO mode (for local development or CI scripts): bun run dev:mcp
   • HTTP mode (expose via HTTP endpoints): bun run start:mcp

Notes

• You can also run package-specific commands from the root using bun --cwd packages/mcp <script> if you prefer targeting only the MCP package.
• Run tests and quality checks as needed: bun test bun run check

Environment variables: The MCP server reads keys from the environment (for example, API keys for You.com services). Start by copying .env.example to .env and populating necessary keys. If you encounter API key errors during tests, ensure YDC_API_KEY is set and sourced in your shell before running tests (source .env).

Common issues:

• Mismatched Node/Bun versions: Ensure Bun is updated to a compatible version (>= 1.2.21) as required by the workspace scripts.
• Dependency hoisting or workspace resolution: Use bun install at the repository root to ensure all workspace links are properly set.
• API rate limits during tests: Use test doubles or mock services if your tests rely on external API calls.

Configuration tips:

• Use the development mode for rapid iterating on features within the MCP server; switch to HTTP mode when you need to validate network-based queries.
• The MCP server patterns rely on standardized mcp-patterns tooling in the monorepo; consult .claude/skills and AGENTS.md for guidance on schemas, error handling, and logging conventions.