Skip to main content
Glama
tschoonj

Repology MCP Server

by tschoonj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_projectsA

Search for projects by name substring.

Args:
    query: Search term to match against project names
    limit: Maximum number of results (default: 10, max: 100)
    maintainer: Optional maintainer email filter
    category: Optional category filter
    inrepo: Optional repository presence filter
    notinrepo: Optional repository absence filter

Returns:
    JSON formatted list of matching projects with their packages
get_projectA

Get detailed information about a specific project.

Args:
    project_name: Exact name of the project to retrieve
    repository: Optional repository filter to show only packages from that repository

Returns:
    JSON formatted list of packages for the project
list_projectsA

List projects with optional filtering.

Args:
    start_from: Project name to start listing from
    limit: Maximum number of results (default: 10, max: 200)
    maintainer: Filter by maintainer email
    category: Filter by category
    inrepo: Filter by repository presence
    notinrepo: Filter by repository absence
    repos: Filter by number of repositories (e.g., "1", "5-", "-5", "2-7")
    families: Filter by number of repository families
    newest: Show only newest projects
    outdated: Show only outdated projects
    problematic: Show only problematic projects

Returns:
    JSON formatted dictionary of projects and their packages
get_repository_problemsB

Get problems reported for a specific repository.

Args:
    repository: Repository name (e.g., "freebsd", "debian")
    start_from: Project name to start from for pagination

Returns:
    JSON formatted list of problems for the repository
get_maintainer_problemsB

Get problems reported for packages maintained by a specific person.

Args:
    maintainer: Maintainer email address
    repository: Optional repository to limit results to
    start_from: Project name to start from for pagination

Returns:
    JSON formatted list of problems for the maintainer

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources