Skip to main content
Glama
alyiox

mcp-atlassian-attachments

by alyiox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-atlassian-attachments

No user-submitted related servers found.

    Related Servers

    • jira-dev-mcp

      nianyi778
      A
      license
      A
      quality
      F
      maintenance
      A local MCP server for Jira Cloud-driven development. Connects MCP clients to Jira for searching issues, reading tasks, parsing attachments, and mapping projects to local repos.
      10
      11 npm
      MIT

    • MCP Atlassian

      sooperset
      A
      license
      Not graded
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.
      5,890
      MIT

    • jira-mcp

      fajarmf
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that integrates with Atlassian Jira to search issues, retrieve details, access comments, create new issues, and update issues.
      408 npm
      MIT

    • jira-multi-mcp

      quaz579
      A
      license
      Not graded
      quality
      B
      maintenance
      A single MCP server that lets users interact with multiple Jira Cloud sites at once, routing requests by issue-key prefix and supporting attachment download/upload to disk.
      MIT

    • MCP Atlassian

      uchinx
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.
      1
      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.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools.

    Naming Consistency5/5

    The single tool uses a clear verb_noun pattern (download_jira_attachment), consistent with good naming conventions.

    Tool Count2/5

    The server is named 'attachments' but provides only a download tool; this is far too few for the implied scope.

    Completeness2/5

    Missing fundamental operations like upload, delete, or list attachments, leaving agents with a dead-end workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources