Skip to main content
Glama
vuavada

devflow-mcp

by vuavada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to devflow-mcp

No user-submitted related servers found.

    Related Servers

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      43 npm
      MIT

    • jira-mcp

      mrqwer
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for Jira Server/Data Center that enables Claude and Codex to manage issues, comments, transitions, worklogs, and links through the Jira REST API v2 using Basic Auth.
      -

    • jira-lite-mcp

      pilloom
      F
      license
      A
      quality
      B
      maintenance
      A lightweight Jira Cloud MCP server for Claude Code that provides high-value tools for reading and writing Jira issues with human-readable responses.
      15
      -

    • jira-mcp

      zhiyue
      A
      license
      B
      quality
      D
      maintenance
      MCP server providing access to JIRA data with relationship tracking, optimized payloads, and data cleaning for AI contexts. Supports both Jira Cloud and Server/Data Center.
      9
      8 npm
      MIT

    • Jira MCP Server

      InfinitIQ-Tech
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with Jira's REST API using natural language commands, allowing users to manage Jira projects, issues, comments, and workflows through Claude Desktop and other MCP clients.
      10
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a unique, well-defined purpose. GitLab and Jira tools are cleanly separated by prefixes, and within each domain, tools target distinct resources (e.g., commits, MRs, pipelines, issues, attachments) with no functional overlap.

    Naming Consistency5/5

    All tools follow a consistent `domain_verb_noun` pattern in snake_case. GitLab tools start with `gitlab_` and Jira tools with `jira_`, and verbs like `get_`, `search_`, `download_` are used uniformly.

    Tool Count4/5

    With 22 tools, the server covers two distinct domains (GitLab and Jira) comprehensively. While slightly above the typical 3-15 range, each tool addresses a specific need for developer workflows, justifying the count.

    Completeness3/5

    The tools comprehensively cover read operations for GitLab (commits, files, MRs, pipelines, code search) and Jira (issues, epics, sprints, attachments, comments). However, write operations (creating/updating MRs or issues) are absent, leaving a gap for lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources