Ubuntu MCP Servers
Provides tools for querying and managing bugs and merge requests on GitHub, including searching and submitting bugs, and fetching merge requests.
Provides tools for querying and managing bugs, packages, versions, and merge requests on Launchpad, including searching and submitting bugs, fetching package details, and retrieving version information.
Provides tools for querying package and version information on Snapcraft, including fetching package details and version data.
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., "@Ubuntu MCP Servers search for bugs about snapd"
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.
Ubuntu MCP Servers
MCP servers for querying and submitting Ubuntu data via ubq. Each server exposes a focused set of tools and resources for a single data domain — bugs, packages, versions, or merge requests.
Requirements
Python >= 3.13
uv (recommended) or pip
Related MCP server: quads-mcp
Installation
git clone https://github.com/lvoytek/ubuntu-mcp.git && cd ubuntu-mcp
uv syncThis installs the five entry-point commands:
Command | Server |
| Bug data |
| Package data |
| Package version data |
| Merge request data |
| All of the above at once |
Running a server
All servers share the same CLI flags:
ubuntu-mcp-bugs # streamable-http on 0.0.0.0:8000 (default)
ubuntu-mcp-bugs --transport streamable-http --host 127.0.0.1 --port 9000
ubuntu-mcp-bugs --transport stdio # for MCP clients that spawn the processReplace ubuntu-mcp-bugs with any of the commands above.
Running all servers
Use ubuntu-mcp-all to start every server at once on sequential ports:
ubuntu-mcp-all # bugs=8000, packages=8001, versions=8002, merge-requests=8003
ubuntu-mcp-all --host 127.0.0.1 --port 9000 # bugs=9000, packages=9001, versions=9002, merge-requests=9003Connecting an MCP client
For an HTTP server, add the URL to your client config:
{
"mcp": {
"ubuntu-mcp-bugs": {
"type": "remote",
"url": "http://127.0.0.1:8000/mcp"
},
"ubuntu-mcp-packages": {
"type": "remote",
"url": "http://127.0.0.1:8001/mcp"
},
"ubuntu-mcp-versions": {
"type": "remote",
"url": "http://127.0.0.1:8002/mcp"
},
"ubuntu-mcp-merge-requests": {
"type": "remote",
"url": "http://127.0.0.1:8003/mcp"
}
}
}For stdio, point the client at the entry-point command directly.
Authentication
Most tools require an authenticated session before they can query data. Call login_provider first.
Launchpad
Launchpad supports three authentication modes:
Mode | When |
Anonymous | No credentials provided — read-only public access. Best for CI or headless environments. |
Credential file |
|
Inline token |
|
A default credential file path is also checked automatically: ~/.config/ubq/launchpad-credentials. If this file exists and no other credentials are provided, its contents are used as the token.
Anonymous (no credentials)
{
"tool": "login_provider",
"arguments": { "provider_name": "launchpad" }
}Credential file
{
"tool": "login_provider",
"arguments": {
"provider_name": "launchpad",
"credential_file": "/path/to/launchpad-token"
}
}Inline token
{
"tool": "login_provider",
"arguments": {
"provider_name": "launchpad",
"token": "oauth-token-value"
}
}GitHub
GitHub requires a personal access token passed via token:
{
"tool": "login_provider",
"arguments": {
"provider_name": "github",
"token": "ghp_xxxxxxxxxxxx"
}
}Snapcraft
Snapcraft requires a token passed via token:
{
"tool": "login_provider",
"arguments": {
"provider_name": "snapcraft",
"token": "snap-token-value"
}
}Servers and tools
Bugs — ubuntu-mcp-bugs
Tool | Description |
| Authenticate with a bug data provider |
| List available bug data provider names |
| Fetch a bug by ID |
| Search bugs by criteria |
| Submit a new bug |
Resources:
ubq://bugs/providers— available bug data providersubq://bugs/sessions— active bug data provider sessions
get_bug
bug_id: str — the bug ID
provider_name: str — e.g. "launchpad" or "github"
metadata_only: bool — set True to skip comments and taskssearch_bugs
provider_name: str — e.g. "launchpad" or "github"
title: str | None — filter by title substring
tags: list[str] | None — filter by tags
status: str | None — e.g. "New", "Fix Released"
importance: str | None — e.g. "Medium", "High"
owner: str | None — username of the bug owner
assignee: str | None — username of the assignee
milestone: str | None — milestone name
created_since: str | None — ISO 8601 date (e.g. "2025-01-01")
created_before: str | None — ISO 8601 date
modified_since: str | None — ISO 8601 datesubmit_bug
title: str — bug title (required)
provider_name: str — e.g. "launchpad" or "github"
package_names: list[str] — affected package names
description: str | None — bug description
importance: str | None — e.g. "Medium"
status: str | None — e.g. "New"
tags: list[str] | None — tags to apply
assignee: str | None — username to assign
private: bool — mark the bug private (default False)
milestone: str | None — target milestonePackages — ubuntu-mcp-packages
Tool | Description |
| Authenticate with a package data provider |
| List available package data provider names |
| Fetch a package by name |
Resources:
ubq://packages/providers— available package data providersubq://packages/sessions— active package data provider sessions
get_package
package_name: str — the source package name
provider_name: str — e.g. "launchpad" or "snapcraft"Versions — ubuntu-mcp-versions
Tool | Description |
| Authenticate with a version data provider |
| List available version data provider names |
| Fetch the version of a package in an Ubuntu series |
Resources:
ubq://versions/providers— available version data providersubq://versions/sessions— active version data provider sessions
get_version
package_name: str — the source package name
series: str — Ubuntu codename (e.g. "noble", "jammy")
provider_name: str — e.g. "launchpad" or "snapcraft"
pocket: str | None — "Release", "Security", "Updates", "Proposed", or None for defaultMerge Requests — ubuntu-mcp-merge-requests
Tool | Description |
| Authenticate with a merge request provider |
| List available merge request provider names |
| Fetch a merge request by ID |
| Fetch merge requests assigned to a user |
Resources:
ubq://merge-requests/providers— available merge request providersubq://merge-requests/sessions— active merge request provider sessions
get_merge_request
merge_request_id: str — the merge request ID
provider_name: str — e.g. "launchpad" or "github"get_merge_requests_from_user
user_id: str — username
provider_name: str — e.g. "launchpad" or "github"Available providers
Provider | Domains |
| Bugs, packages, versions, merge requests |
| Bugs, merge requests |
| Packages, versions |
Development
uv sync # install all dependencies
uv run ruff check . # lint
uv run pytest tests/ -v # run testsLicense
GPL-3.0
Available Tools
5 toolsget_bugA
Fetch a bug by ID from the given provider.
Set metadata_only to True to skip fetching comments and tasks.
Inputs: bug_id (required), provider_name (required), metadata_only. Returns: result
list_bug_providersA
List all available bug data provider names.
Inputs: no named parameters. Returns: result
login_providerA
Authenticate with a bug data provider (e.g. 'launchpad', 'github').
For Launchpad: provide a token directly, a credential file path containing the token, or omit both to authenticate anonymously.
Inputs: provider_name (required), username, token, credential_file. Returns: result
search_bugsB
Search for bugs matching criteria on the given provider.
Date arguments should be ISO 8601 format (e.g. '2025-01-01').
Inputs: provider_name (required), title, tags, status, +7 more. Returns: result
submit_bugC
Submit a new bug to the given provider.
Returns the created bug record, or None on failure.
Inputs: title (required), provider_name (required), package_names, description, +6 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct operation: listing providers, authentication, searching, fetching by ID, and submitting. No overlaps or ambiguity.
All tool names follow a consistent verb_noun pattern with underscore separation (e.g., get_bug, list_bug_providers, login_provider, search_bugs, submit_bug).
Five tools cover the essential bug tracking workflow without being excessive or insufficient for a focused server.
Basic operations (list, auth, search, get, create) are present, but update and delete/close operations are missing, leaving minor gaps in full lifecycle management.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Trust, freshness, policy, and discovery layer for public MCP servers.
Remote MCP server for managing Muninx tickets, messages, ticket search, and support analytics.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceUnified MCP server for Git forge management across GitHub, GitLab, Gitea, and Bitbucket, enabling repository, issue, PR, and CI/CD operations via CLI tools and APIs.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.MIT
- FlicenseAqualityDmaintenanceMCP server for JetBrains Space merge requests and Patronus CI dry runs, enabling creation, viewing, and management of merge requests as well as starting and monitoring CI dry runs.16-
- AlicenseNot gradedqualityCmaintenanceCollection of MCP servers for Forgejo, NetBox, Authentik, and CouchDB, enabling issue tracking, device management, authentication, and database operations via MCP and CLI.GPL 3.0