Web search, AI agent, and content extraction via You.com APIs
Open-source monorepo for AI-powered development - npm packages and development skills for building with You.com's AI capabilities.
Build with You.com's AI capabilities across your entire workflow:
Production-ready packages for building, testing, and shipping agentic workflows:
CLI tool and shared TypeScript utilities for You.com API - provides command-line interface and type-safe building blocks used by MCP and AI SDK packages. Documentation →
MCP Server giving AI agents real-time web search, AI answers, and content extraction via Model Context Protocol. Documentation →
Vercel AI SDK plugin for You.com web search and AI agents - zero server setup, works with any model provider. Documentation →
Use Claude models (Opus, Sonnet, Haiku) in Microsoft Teams.ai apps - drop-in replacement for OpenAI with full streaming support. Documentation →
Project-specific development patterns and workflows are in .claude/skills/:
These skills are used by AI coding assistants when contributing to dx-toolkit packages. View development guide →
Prerequisites:
brew install gh (macOS) or other platformsDevelopment setup:
# Clone repository
git clone git@github.com:youdotcom-oss/dx-toolkit.git
cd dx-toolkit
# Install dependencies
bun install
# Set up environment variables
cp .env.example .env
# Edit .env and add your YDC_API_KEY
source .env
# Authenticate with GitHub (if using gh CLI)
gh auth login
# Build all packages
bun run build
# Run all tests
bun test
# Run all quality checks
bun run check
Troubleshooting tests: If you get API key errors when running tests:
.env file exists with YDC_API_KEY=your-keysource .env to load environment variablesbun testFor comprehensive development guidelines, see AGENTS.md.
This toolkit uses Bun workspaces. Commands can run at workspace-level (all packages) or package-level (specific package).
Run from repository root to affect all packages:
bun install # Install dependencies for all packages
bun run build # Build all packages
bun test # Test all packages
bun run check # Run all quality checks (biome + types + package)
bun run check:write # Auto-fix all issues across all packages
From Root - Two patterns available:
# Pattern 1: Root shortcuts (defined in root package.json)
bun run dev:mcp # Start MCP server in STDIO mode
bun run start:mcp # Start MCP server in HTTP mode
bun run test:mcp # Test MCP server only
# Pattern 2: Direct package commands with bun --cwd
bun --cwd packages/mcp dev # Start MCP server in dev mode
bun --cwd packages/mcp start # Start MCP server in HTTP mode
bun --cwd packages/mcp test # Test MCP server
bun --cwd packages/mcp check # Run quality checks
# Use bun --cwd for any package script:
bun --cwd packages/api test
bun --cwd packages/ai-sdk-plugin build
bun --cwd packages/teams-anthropic check
From Package Directory:
cd packages/mcp
bun dev # Start in development mode
bun test # Run tests
bun run check # Check code quality
Contributions are welcome! See CONTRIBUTING.md for guidelines.
MIT - See LICENSE for details
Built with ❤️ by You.com
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @youdotcom-oss/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-youdotcom-oss-mcp": {
"command": "npx",
"args": [
"-y",
"@youdotcom-oss/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@youdotcom-oss/mcpnpmYou.com Web Access & AI works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.