Skip to main content
Glama
GeiserX

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to atlassian-browser-mcp

No user-submitted related servers found.

    Related Servers

    • jira-run-mcp

      cuongph-dev-work
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for Jira 8 that enables SSO-authenticated issue management, work logging, search, and more through natural language, using Playwright for session setup and running as a local subprocess.
      10 npm
      MIT

    • mcp-browser

      souhailmerroun-recyclebin
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.
      -

    • atlassian-browser-mcp

      tinyc0der
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables accessing Jira and Confluence using browser cookies captured via a Chrome extension, avoiding the need for API tokens or browser automation. It wraps the mcp-atlassian toolset and works with Atlassian Cloud and Server/Data Center behind SSO.
      1
      GPL 3.0

    • kilogent-browser

      codebridger
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.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.8/5.0

    Scored across 91 tools

    Disambiguation5/5

    Tools are clearly separated by prefix (confluence_ vs jira_) and within each, they use distinct verb_noun combinations. No overlapping purposes; each tool has a unique, well-defined function.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern across both Confluence and Jira sets. Verbs like create, get, update, delete, add, search are used uniformly.

    Tool Count2/5

    With 91 tools, the server is overly broad, covering two major products with many specialized functions. This makes it heavy and harder to navigate; splitting into separate Jira and Confluence servers would improve coherence.

    Completeness4/5

    The tool set covers a comprehensive range of operations for both Jira and Confluence, including CRUD, search, permissions, attachments, comments, and advanced features. Minor gaps exist, such as no delete comment or space management tools.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources