Skip to main content
Glama
iwilldotdev

dev.mcp

by iwilldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to dev.mcp

No user-submitted related servers found.

    Related Servers

    • MCP Setup Server

      lakshmidevi2016
      F
      license
      Not graded
      quality
      D
      maintenance
      A modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.
      -

    • Work Integrations MCP

      NazarKY
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.
      558 npm
      MIT

    • Jira MCP Server

      msadegh76
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to search, create, update, and manage Jira issues, users, and projects via natural language, using the Jira REST API and MCP stdio transport.
      558 npm
      MIT

    • mcp-jira-stdio

      freema
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Jira integration with stdio transport. Enables reading, writing, and managing Jira issues and projects directly from Claude Desktop. Supports issue creation, updates, comments, JQL search, and project management.
      23
      1,787 npm
      14
      MIT

    • cyber-figma

      cyberuni
      A
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server exposing Figma REST API tools to AI agents, enabling file reads, comments, variables, and other resource operations. Works with personal access tokens and integrates with Claude, Cursor, Codex, and more.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.9/5.0

    Scored across 55 tools

    Disambiguation4/5

    Tools are grouped by product prefix and target distinct resource/action pairs, so most are easy to tell apart even at 55 tools. The main risk is within Figma where get_file/get_metadata/get_design_context and get_screenshot/download_assets have adjacent image/export purposes, though the descriptions provide enough separation.

    Naming Consistency4/5

    Nearly all tools follow a product_verb_noun snake_case pattern (confluence_create_page, jira_transition_issue), which is highly predictable. Deviations like figma_whoami/gitlab_whoami and the ambiguous gitlab_save_merge_request (create-or-update) keep it from a perfect score.

    Tool Count1/5

    At 55 tools this server presents an extreme selection burden, far beyond the 25+ threshold; it effectively bundles four product-specific servers into one namespace. The per-platform subsets are reasonable, but the aggregate would be better split into separate MCP servers.

    Completeness4/5

    Core lifecycles are covered for all four platforms: Confluence pages/comments, GitLab MRs/issues/pipelines/files, Jira issues/transitions/comments/worklogs/links, and Figma read/export/context. Missing operations are mostly destructive ones (deletes, comment updates) that can be worked around or are rarely needed in AI-assisted dev workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources