Skip to main content
Glama
tschoonj

Repology MCP Server

by tschoonj
README.md
# Repology MCP Server

<!-- mcp-name: io.github.tschoonj/repology-mcp-server -->

[![CI](https://github.com/tschoonj/repology-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/tschoonj/repology-mcp-server/actions/workflows/ci.yml)
[![Docker](https://github.com/tschoonj/repology-mcp-server/actions/workflows/docker.yml/badge.svg)](https://github.com/tschoonj/repology-mcp-server/actions/workflows/docker.yml)
[![Docker Image](https://img.shields.io/badge/docker-ghcr.io%2Ftschoonj%2Frepology--mcp--server-blue)](https://github.com/tschoonj/repology-mcp-server/pkgs/container/repology-mcp-server)
[![PyPI](https://img.shields.io/pypi/v/repology-mcp-server)](https://pypi.org/project/repology-mcp-server/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A Model Context Protocol (MCP) server that provides access to the [Repology](https://repology.org) package repository data through a standardized interface.

## Features

This MCP server exposes the following tools:

- **search_projects**: Search for projects by name
- **get_project**: Get detailed information about a specific project
- **list_projects**: List projects with optional filtering
- **get_repository_problems**: Get problems reported for repositories
- **get_maintainer_problems**: Get problems reported for specific maintainers

## Installation

### Using uv (recommended)

```bash
# Install dependencies
uv sync

# Install in development mode
uv pip install -e .
```

### Using pip

```bash
pip install -e .
```

## Usage

### As a standalone server

```bash
# Run with stdio transport (for Claude Desktop, etc.)
repology-mcp-server

# Run with HTTP transport
repology-mcp-server --transport http --port 8000
```

### With Claude Desktop

Add to your Claude Desktop configuration:

```json
{
  "mcpServers": {
    "repology": {
      "command": "uv",
      "args": ["run", "repology-mcp-server"]
    }
  }
}
```

Or using the pre-built Docker image:

```json
{
  "mcpServers": {
    "repology": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/tschoonj/repology-mcp-server:latest"]
    }
  }
}
```

### With VS Code

Add to your VS Code settings (`.vscode/settings.json` or user settings):

```json
{
  "mcp.servers": {
    "repology": {
      "command": "uv",
      "args": ["run", "repology-mcp-server"]
    }
  }
}
```

Or using the pre-built Docker image:

```json
{
  "mcp.servers": {
    "repology": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/tschoonj/repology-mcp-server:latest"]
    }
  }
}
```

### As a development server

```bash
# Run in development mode with MCP inspector
uv run mcp dev src/repology_mcp/server.py
```

### Using Docker

#### Pre-built images from GitHub Container Registry

```bash
# Pull the latest image
docker pull ghcr.io/tschoonj/repology-mcp-server:latest

# Run with stdio transport
docker run -i --rm ghcr.io/tschoonj/repology-mcp-server:latest

# Run with HTTP transport on port 8000
docker run --rm -p 8000:8000 ghcr.io/tschoonj/repology-mcp-server:latest --transport http --port 8000

# Use a specific version
docker pull ghcr.io/tschoonj/repology-mcp-server:1.0.0
docker run -i --rm ghcr.io/tschoonj/repology-mcp-server:1.0.0
```

#### Local development with Docker

```bash
# Build the Docker image locally
docker build -t repology-mcp-server .

# Run with stdio transport
docker run -i --rm repology-mcp-server

# Run with HTTP transport on port 8000
docker run --rm -p 8000:8000 repology-mcp-server --transport http --port 8000
```

## Development

### Setup

```bash
# Clone the repository
git clone <repository-url>
cd repology-mcp-server

# Install development dependencies
uv sync --extra dev
```

### Running tests

```bash
# Run all tests
uv run pytest

# Run with coverage
uv run pytest --cov=repology_mcp --cov-report=html

# Run specific test file
uv run pytest tests/test_client.py -v
```

### Code formatting

```bash
# Format code
uv run black src tests
uv run isort src tests

# Type checking
uv run mypy src
```

## API Reference

### Tools

#### search_projects
Search for projects by name substring.

**Parameters:**
- `query` (string): Search term to match against project names
- `limit` (integer, optional): Maximum number of results (default: 10, max: 100)

#### get_project
Get detailed package information for a specific project.

**Parameters:**
- `project_name` (string): Exact name of the project to retrieve

#### list_projects  
List projects with optional filtering.

**Parameters:**
- `start_from` (string, optional): Project name to start listing from
- `limit` (integer, optional): Maximum number of results (default: 10, max: 200)
- `maintainer` (string, optional): Filter by maintainer email
- `category` (string, optional): Filter by category
- `inrepo` (string, optional): Filter by repository presence
- `notinrepo` (string, optional): Filter by repository absence

#### get_repository_problems
Get problems reported for a specific repository.

**Parameters:**
- `repository` (string): Repository name (e.g., "freebsd", "debian")
- `start_from` (string, optional): Project name to start from for pagination

#### get_maintainer_problems  
Get problems reported for packages maintained by a specific person.

**Parameters:**
- `maintainer` (string): Maintainer email address
- `repository` (string, optional): Limit to specific repository
- `start_from` (string, optional): Project name to start from for pagination

## License

MIT License - see LICENSE file for details.

## Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests for new functionality
5. Run the test suite
6. Submit a pull request

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_maintainer_problems and get_repository_problems focus on problem reporting for different entities, get_project retrieves detailed project information, list_projects provides filtered listings, and search_projects enables name-based searching. There is no overlap in functionality that would cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case: get_maintainer_problems, get_project, get_repository_problems, list_projects, search_projects. The naming is predictable and follows the same convention throughout.

Tool Count5/5

With 5 tools, this server is well-scoped for a Repology interface. Each tool serves a specific purpose in querying projects, problems, and repositories, making the count appropriate without being too sparse or bloated.

Completeness4/5

The toolset covers core Repology operations well: retrieving projects (get_project, list_projects, search_projects) and problem reporting (get_maintainer_problems, get_repository_problems). Minor gaps might include updating or managing data, but these are likely read-only operations for this domain, so coverage is good.

Maintenance

ActivityInactive
ResponsivenessNo issues