Bitbucket Pipelines MCP Server

Created By
ygorpintoa year ago
Bitbucket Pipelines MCP is a Model Context Protocol (MCP) server that provides tools for interacting with Bitbucket Pipelines. This server implements the MCP standard, enabling language models like Claude to manage Bitbucket Pipelines through a standardized interface.
Overview

What is Bitbucket Pipelines MCP?

Bitbucket Pipelines MCP is a Model Context Protocol (MCP) server that provides tools for interacting with Bitbucket Pipelines, enabling language models to manage pipelines through a standardized interface.

How to use Bitbucket Pipelines MCP?

To use the server, clone the repository, configure environment variables, and run the server using Docker or locally. You can interact with the server using provided tools or directly through commands.

Key features of Bitbucket Pipelines MCP?

  • Implements the Model Context Protocol for seamless integration with language models.
  • Provides tools for listing, triggering, and managing Bitbucket pipelines.
  • Supports environment variable configuration for secure access.

Use cases of Bitbucket Pipelines MCP?

  1. Automating CI/CD processes in Bitbucket.
  2. Integrating with language models for enhanced pipeline management.
  3. Managing multiple pipelines efficiently through a standardized interface.

FAQ from Bitbucket Pipelines MCP?

  • What is the Model Context Protocol?

It is a protocol that standardizes the interaction between language models and various tools, allowing for easier integration and management.

  • Is there a Docker setup available?

Yes, the recommended setup is through Docker, which simplifies the installation and execution process.

  • Can I run this server locally?

Yes, you can run the server locally by following the installation instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ygorpinto
Star
0
Language
TypeScript
License
MIT 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)

a day ago
Crevio

2 days ago