Skip to main content
Glama
koosty

yacy-mcp

by koosty
README.md
# YaCy MCP Server

MCP (Model Context Protocol) Server implementation that provides AI tools to search using YaCy web search API.

## Installation

1. Make sure you have `uv` installed:

```bash
pip install uv
```

2. Install the package in development mode:

```bash
cd yacy-mcp
uv sync  # Sync all dependencies from pyproject.toml and uv.lock
```

Or alternatively:

```bash
cd yacy-mcp
uv pip install -e .
```

## Usage

1. Make sure you have a YaCy server running (typically on http://localhost:8090)
2. Set environment variables (optional):

```bash
export YACY_URL=http://localhost:8090
```

3. Run the MCP server:

```bash
python -m yacy_mcp
```

## Configuration

The server can be configured using environment variables:

- `YACY_URL`: URL of your YaCy instance (default: http://localhost:8090)

## Available Tools

- `yacy-search`: Search using YaCy web search engine
  - Parameters:
    - `query` (string, required): Search query string
    - `max_results` (integer, optional): Maximum number of results to return (default: 10)
    - `resource` (string, optional): Search resource (local or global, default: global)

## MCP Configuration for AI Applications

To use this server with AI applications that support the Model Context Protocol (MCP), configure your MCP client to connect to the server using stdio transport.

Example configuration for Claude Desktop (settings.json):
```json
{
  "mcpServers": {
    "yacy-mcp": {
      "command": "uvx",
      "args": ["yacy_mcp"],
      "env": {
        "YACY_URL": "http://localhost:8090"
      }
    }
  }
}
```

For other MCP-compatible applications, use the command `uvx yacy_mcp` as the server executable. The server will be automatically fetched and run from PyPI.

## Integration with AI Applications

This MCP server can be used with AI applications that support the Model Context Protocol to perform web searches using the YaCy search engine.

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as a web search operation.

Naming Consistency4/5

The single tool name 'yacy_search' is descriptive and follows a verb-like pattern, but with only one tool there is no pattern to compare against for consistency.

Tool Count2/5

A single search tool is too few for a full-featured MCP server, even one focused on a single search engine. Users would expect additional capabilities like managing resources or getting engine status.

Completeness2/5

The search tool provides the core search functionality, but lacks any supporting operations such as retrieving specific results, filtering, or examining engine state. This leaves significant gaps for agents that might need more than a basic search.

Maintenance

ActivityInactive
ResponsivenessNo issues