Skip to main content
Glama
lvoytek

Ubuntu MCP Servers

by lvoytek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Ubuntu MCP Servers

No user-submitted related servers found.

    Related Servers

    • quads-mcp

      grafuls
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.
      MIT

    • mcp-tools

      stef7
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP servers to interact with WordPress sites via REST API, supporting multiple sites and aggregated tools.
      -

    • mcpkit

      MDReal32
      A
      license
      Not graded
      quality
      A
      maintenance
      A single MCP server that runs many bundled integrations — GitHub, GitLab, Jira, Confluence — from declarative JSON manifests, exposing all of their tools over one stdio connection. It enables discovering repositories, issues, merge requests, pages and pipelines, and creating or transitioning them, with per-server authentication handled by the executor.
      MIT

    • space-mcp

      bindreams
      F
      license
      A
      quality
      D
      maintenance
      MCP 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
      -

    • mcp-tools

      gilfreund
      A
      license
      Not graded
      quality
      C
      maintenance
      Collection 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
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing providers, authentication, searching, fetching by ID, and submitting. No overlaps or ambiguity.

    Naming Consistency5/5

    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).

    Tool Count5/5

    Five tools cover the essential bug tracking workflow without being excessive or insufficient for a focused server.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources