Atlassian Bitbucket MCP Server

Created By
aasharia year ago
Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.
Overview

What is the Atlassian Bitbucket MCP Server?

The Atlassian Bitbucket MCP Server is a TypeScript-based Model Context Protocol (MCP) server designed for integrating AI systems like Claude with Atlassian Bitbucket, allowing access to repositories, pull requests, and workspace data.

How to use the Atlassian Bitbucket MCP Server?

To use the server, configure it with your Atlassian or Bitbucket credentials and run it via command line or integrate it with AI clients like Claude Desktop or Cursor AI.

Key features of the Atlassian Bitbucket MCP Server?

  • MCP Server: Connects AI clients to Bitbucket resources.
  • Bitbucket Integration: Access to repositories and pull requests.
  • CLI Support: Execute commands directly from the command line.
  • Flexible Configuration: Supports environment variables and config files.
  • Development Tools: Includes MCP Inspector for debugging.

Use cases of the Atlassian Bitbucket MCP Server?

  1. Automating repository management tasks.
  2. Integrating AI assistants for enhanced productivity.
  3. Accessing pull request data for analysis.

FAQ from the Atlassian Bitbucket MCP Server?

  • Can I use this server with any Bitbucket instance?

Yes, as long as you have the correct credentials and permissions.

  • Is there a graphical interface for this server?

No, it primarily operates through command line and integrates with AI clients.

  • What programming language is this server written in?

The server is written in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aashari
Star
23
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago