Skip to main content
Glama
Copr MCP

Copr MCP

Official
by fedora-copr

Copr MCP

Demo

Please see the First look at the Copr MCP server.

Demo

Prerequisites

Install dependencies

uv sync

Related MCP server: TeamCity MCP Server

MCP Usage

Register the MCP server with Claude Code, Codex, Cursor, or any other agent.

Claude Code

To register the copr server with Claude Code, execute this command

$ claude mcp add copr --scope user \
    -- uv run --directory "$(pwd)" python main.py

If you don't need this MCP server anymore, uninstall it.

$ claude mcp remove copr

Codex

$ codex mcp add copr -- uv run --directory "$(pwd)" python main.py

If you don't need this MCP server anymore, uninstall it.

$ codex mcp remove copr

Cursor

If you use Cursor, open or create ~/.cursor/mcp.json and add the copr entry to the list of mcpServers.

Change the directory (~/src/copr-mcp) to wherever you've cloned this copr-mcp project.

{
  "mcpServers": {
    "copr": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "~/src/copr-mcp",
        "python",
        "main.py"
      ]
    }
  }
}

If you don't need this MCP server anymore, removing the copr entry from the mcpServers list in ~/.cursor/mcp.json.

Visual Studio Code

Open the Command Palette in VSCode by pressing Ctrl+Shift+P. Then type >MCP: Open User Configuration. The file mcp.json that opens should look something like this:

{
	"servers": {}
}

Add the copr MCP server like so:

{
  "servers": {
    "copr": {
      "type": "local",
      "command": "uvx",
      "args": ["--from", "git+https://github.com/fedora-copr/copr-mcp@main", "--verbose", "copr-mcp-server"]
    }
  }
}

Save the file (~/.config/Code/mcp.json) and start the server by hitting the little "Save" link that appears right above the line with "copr": {.

Test the server by opening the Chat view with Ctrl+Alt+I. Then type the following and press Enter:

Use copr_list_mock_chroots from the copr MCP server and list all supported mock chroots.

You should see a Run copr_list_mock_chroots copr (MCP Server) followed by some text and a button that says Allow in this Session.

If you don't need this MCP server anymore, remove the copr entry from the servers list in the MCP: Open User Configuration (~/.config/Code/mcp.json).

Run tools

Once the MCP server is registered, go to i.e. Claude or Cursor and ask it questions like

Tell me the status of Copr build 8101723

Can you give me last 5 builds from the frostyx/foo Copr project?

Build the DistGit package hello in my frostyx/foo project

Create a Copr project frostyx/foo with a fedora-43-x86_64 chroot

Development

Go to https://console.anthropic.com, "API Keys" and generate a new key. Then export it in your terminal:

$ export ANTHROPIC_API_KEY=...

Then run

$ uv run main.py --prompt "Tell me the status of Copr build 8101723"

To use a different model pass --model

$ uv run main.py --model gpt-5-mini --prompt "Tell me the status of Copr build 8101723"

Full list of models can be found here: https://pydantic.dev/docs/ai/api/models/base/#pydantic_ai.models.KnownModelName

Tests

$ uv run mypy .
$ uv run ruff check
$ uv run pytest

Available Tools

10 tools
auth_checkC

Call an endpoint protected by login to check whether the user auth key is valid

:return: Munch

Inputs: no named parameters.

copr_build_statusB

Get the status of a Copr build by its ID.

Inputs: build_id (required). Returns: id, state, name

copr_create_projectA

Create a Copr project with a given name for a specified owner. When creating a new project, at least one chroot must be specified. For example fedora-rawhide-x86_64

Inputs: ownername (required), projectname (required), chroots (required). Returns: id, web_url, ownername, name, +1 more

copr_enable_repositoryB

Provide instructions for enabling a Copr repository on the user system. This requires root privileges and must be run manually by the user.

Inputs: ownername (required), projectname (required). Returns: result

copr_get_build_logC

Fetch and return the text content of any Copr build log URL.

Inputs: log_url (required). Returns: result

copr_get_build_log_urlA

Returns all log URLs for a Copr build, covering the SRPM builds, the dist-git import, and each per-chroot build.

Inputs: build_id (required). Returns: result

copr_list_buildsB

Get the status of all builds in a Copr project identified by its ownername/projectname.

Inputs: ownername (required), projectname (required). Returns: result

copr_list_mock_chrootsA

Get a list of all mock chroots that you can create or use in copr. The response copr will give may vary over time, i.e. when a new Fedora or RHEL version is released.

Inputs: no named parameters. Returns: result

copr_list_mock_chroots_for_projectA

Get a list of all mock chroots that are configured for a given copr project or nothing if the project could not be found. The response may vary over time, depending on if chroots where added or removed from the copr project.

Inputs: ownername (required), projectname (required). Returns: result

copr_submit_buildC

Submit a new build into a Copr project defined by its ownername and projectname. Copr supports multiple source types, see the documentation https://docs.copr.fedorainfracloud.org/user_documentation.html#build-source-types

Inputs: ownername (required), projectname (required), source (required). Returns: id, web_url, state, submitter

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct function: authentication, project creation, build management (status, logs, list, submit), repository enabling, and mock chroot listing. The two log tools (content vs. URLs) are complementary and clearly differentiated.

    Naming Consistency5/5

    All tools follow a consistent 'copr_verb_noun' pattern with lowercase and underscores, e.g., copr_create_project, copr_list_builds, copr_submit_build. No deviations or mixed conventions.

    Tool Count5/5

    With 10 tools, the server covers the core tasks of a build system without being excessive or sparse. Each tool serves a clear purpose within the Copr domain.

    Completeness4/5

    The tool set covers the main workflow: authentication, project creation, build submission, status checking, log retrieval, and repository enabling. Missing operations like project update/delete or build cancellation are minor gaps, but the core functionality is present.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables users to search and retrieve package repository information from Repology through natural language. Supports searching projects, getting detailed package information, and checking repository problems across multiple Linux distributions and package managers.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.
      16 npm
      MIT