Copr MCP
OfficialThe Copr MCP server lets you interact with Fedora Copr (a build system for RPM packages) to manage builds, projects, and repositories through an AI agent interface.
Check build status – Get the current state of a specific Copr build by ID.
List builds in a project – Retrieve all builds for a given Copr project (
ownername/projectname).Create a project – Create a new Copr project with a specified owner and build chroots (e.g.,
fedora-rawhide-x86_64).Submit builds – Initiate new builds from supported source types like PyPI or DistGit.
Enable a repository – Get instructions for enabling a Copr repository on a user's system.
List mock chroots – List all available mock chroots (build targets) across Fedora/RHEL versions and architectures, or those configured for a specific project.
Get build log URLs – Retrieve log URLs for a build, including SRPM, dist-git import, and per-chroot logs.
Fetch build log content – Download and return the text content of a build log.
Check authentication – Verify whether the user's API auth key is valid.
Provides tools for managing Fedora Copr builds and projects, including checking build status, listing recent builds, building packages, and creating projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Copr MCP List the last 5 builds in frostyx/foo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Copr MCP
Demo
Please see the First look at the Copr MCP server.

Prerequisites
Install dependencies
uv syncRelated 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.pyIf you don't need this MCP server anymore, uninstall it.
$ claude mcp remove coprCodex
$ codex mcp add copr -- uv run --directory "$(pwd)" python main.pyIf you don't need this MCP server anymore, uninstall it.
$ codex mcp remove coprCursor
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 pytestAvailable Tools
10 toolsauth_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
Scored across 10 tools
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.
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.
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.
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
Related MCP Connectors
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Connect your Cormak.app account to manage projects, task boards, AI agents and creative work from your AI assistant. The server exposes up to 83 tools, limited to the OAuth permissions you choose. Organize tasks, read and update project drafts, inspect saved studio results, create product descriptions and images, and request supported photo, video, 3D, voiceover, SEO and advertising operations. Publishing saved projects requires separate owner approval. Reading and ordinary manual task management do not themselves start paid generation. AI operations use credits from your connected Cormak account and require owner confirmation, or an existing bounded spending permission for supported product operations. You can limit and revoke connections in Cormak. The MCP does not provide bank access, payment details or provider API keys. CRM, streaming website generation and business-plan generation are not exposed through this integration. Get started: https://app.cormak.app/mcp Setup guide and examples: https://cormak.app/blog/cormak-mcp-guide Privacy: https://cormak.app/privacy Support: https://cormak.app/contact
Manage projects, tasks, time tracking, and team collaboration through natural language.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables 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.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.16 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables users to interact with Prow CI/CD systems, retrieving build logs and diagnosing PR build issues through natural language.5-

Azure DevOps MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceProvides Azure DevOps tooling for AI agents, enabling interaction with projects, work items, repositories, and pipelines through natural language.128,342 npm2,086MIT