Copr MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| copr_build_statusB | Get the status of a Copr build by its ID. |
| copr_list_buildsB | Get the status of all builds in a Copr project identified by its ownername/projectname. |
| 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 |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| copr_get_build_logC | Fetch and return the text content of any Copr build log URL. |
| auth_checkC | Call an endpoint protected by login to check whether the user auth key is valid :return: Munch |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.