Skip to main content
Glama
deenesjakoruzh
jimbul

You.com MCP Server

by jimbul
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

You.com MCP Server

This MCP (Model Context Protocol) server provides AI assistants with the ability to search the web, get news, and perform research using the You.com API. Feedback welcomed.

Features

  • Web Search: Access to You.com's web search functionality

  • Smart Search: AI-powered answers with citation support

  • Research: Comprehensive, citation-backed answers for academic queries

  • News Search: Latest news articles on any topic

Related MCP server: Kagi MCP Server

Prerequisites

  • Node.js (v16 or higher)

  • npm or yarn

  • You.com API key (get one from api.you.com)

Installation

  1. Clone this repository:

    git clone https://github.com/jimbul/youcom-mcp.git
cd youcom-mcp

  2. Install dependencies:

    npm install

  3. Create a .env file based on the example:

    cp .env.example .env

  4. Add your You.com API key to the .env file:

    YOU_API_KEY=your_actual_api_key_here

  5. Build the project:

    npm run build

Running Locally (Optional)

You can run the server locally for testing:

npm start

Setting up with Claude

To use this MCP server with Claude (Anthropic Assistant), you need to configure Claude to use this server:

  1. Open the Claude extension settings in VS Code:

    • Click on the Claude icon in the VS Code sidebar

    • Click on the settings icon (⚙️) and select "MCP Settings"

  2. Add the following configuration to the mcpServers section:

"youcom-mcp": {
  "autoApprove": [],
  "disabled": false,
  "command": "node",
  "args": [
    "/absolute/path/to/your/youcom-mcp/dist/index.js"
  ],
  "env": {
    "YOU_API_KEY": "your_actual_api_key_here"
  },
  "transportType": "stdio"
}

Important Notes:

  • Replace /absolute/path/to/your/youcom-mcp/dist/index.js with the actual path on your system

  • Replace your_actual_api_key_here with your You.com API key

Usage Examples

Once configured, you can use the MCP tools directly in your conversations with Claude:

Web Search

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>web_search</tool_name>
<arguments>
{
  "query": "latest research on renewable energy"
}
</arguments>
</use_mcp_tool>

Smart Search

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>smart_search</tool_name>
<arguments>
{
  "query": "how do quantum computers work",
  "instructions": "explain in simple terms"
}
</arguments>
</use_mcp_tool>

Research

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>research</tool_name>
<arguments>
{
  "query": "effects of climate change on ocean ecosystems",
  "instructions": "focus on coral reefs"
}
</arguments>
</use_mcp_tool>

News Search

<use_mcp_tool>
<server_name>youcom-mcp</server_name>
<tool_name>news_search</tool_name>
<arguments>
{
  "query": "latest developments in AI"
}
</arguments>
</use_mcp_tool>

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Running evals

The evals package loads an mcp client that then runs the index.ts file, so there is no need to rebuild between tests. You can load environment variables by prefixing the npx command. Full documentation can be found here.

OPENAI_API_KEY=your-key  npx mcp-eval src/evals/evals.ts src/index.ts

License

MIT

Acknowledgements

This project uses the You.com API for search functionality.

Available Tools

4 tools
researchD
ParametersJSON Schema
NameRequiredDescriptionDefault
instructionsNoCustom instructions for tailoring the response (optional)
queryYesThe research query to send to You.com's Research API

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updatesv1.0.0
    • First observednews_search
    • First observedresearch
    • First observedsmart_search
    • First observedweb_search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.4/5.0
Disambiguation1/5

The tools are highly ambiguous with overlapping purposes, as all four tools appear to perform search-related functions without clear distinctions. Without descriptions, it's impossible to differentiate between 'news_search', 'research', 'smart_search', and 'web_search', making them effectively indistinguishable for an agent.

Naming Consistency3/5

The naming shows mixed conventions: 'news_search' and 'web_search' follow a consistent noun_verb pattern, but 'research' and 'smart_search' deviate with different structures. While readable, the inconsistency in verb usage and pattern reduces predictability across the set.

Tool Count3/5

With 4 tools, the count is borderline for a search-focused server, as it feels thin but not unreasonable. However, the lack of descriptions makes it hard to assess if this number adequately covers the domain, suggesting potential under-scoping or redundancy.

Completeness2/5

Inferred as a search server, there are significant gaps in coverage, such as missing filtering, sorting, or result management tools. The surface is severely incomplete for a robust search domain, likely causing agent failures due to limited operational capabilities.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Kagi MCP Server by kagisearch

    Kagi MCP Serverofficial

    kagisearch
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
    2
    502
    MIT

  • Perplexity MCP Server

    RossH121
    A
    license
    A
    quality
    D
    maintenance
    An MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.
    6
    4
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jimbul/youdotcom_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server