Ubuntu MCP Servers
Server 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 |
|---|---|
| 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. |
| list_bug_providersA | List all available bug data provider names. |
| get_bugA | Fetch a bug by ID from the given provider. Set metadata_only to True to skip fetching comments and tasks. |
| search_bugsB | Search for bugs matching criteria on the given provider. Date arguments should be ISO 8601 format (e.g. '2025-01-01'). |
| submit_bugC | Submit a new bug to the given provider. Returns the created bug record, or None on failure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bugs_providers_resource | Available bug data providers. |
| bugs_sessions_resource | Active bug data provider sessions. |
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.