1. Conduid
  2. Developer Tools
  3. Vibucket
MCP server · Developer Tools

Vibucket

MCP server: Vibucket

Unclaimed last commit a year ago devtools
37Low

Scored 4 months ago · breakdown

About Vibucket

Vibucket is an MCP server published by SpeCT in the Developer Tools category: mCP server: Vibucket. It has been installed 0 times through Conduid.

The repository has 2 stars and 0 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx vibucket

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Vibucket

Powered by Claude · Grounded in docs

I know everything about Vibucket. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Bitbucket MCP Server

This directory contains an implementation of a Model Context Protocol (MCP) server that exposes Bitbucket API as tools.

Overview

The Model Context Protocol (MCP) allows applications to provide context for LLMs in a standardized way. This implementation creates an MCP server that exposes Bitbucket API operations as tools that can be consumed by MCP clients, including LLM applications.

Files

  • mcp.ts: The MCP server implementation that exposes Bitbucket API methods as tools
  • example-client.ts: An example client demonstrating how to use the Bitbucket tools

Available Tools

This MCP server exposes the following Bitbucket API operations as tools:

Repository and Pipeline Operations

  1. bitbucket/getRepositories: List repositories for the authenticated user
  2. bitbucket/getRepository: Get details of a specific repository
  3. bitbucket/getPipelines: List pipelines for a repository
  4. bitbucket/getPipeline: Get details of a specific pipeline
  5. bitbucket/getPipelineSteps: List steps for a specific pipeline

Pull Request Operations

  1. bitbucket/getPullRequests: List pull requests for a repository
  2. bitbucket/getPullRequest: Get details of a specific pull request
  3. bitbucket/createPullRequest: Create a new pull request
  4. bitbucket/updatePullRequest: Update an existing pull request
  5. bitbucket/mergePullRequest: Merge a pull request
  6. bitbucket/declinePullRequest: Decline a pull request

Setup

  1. Install dependencies:

    npm install @modelcontextprotocol/sdk zod
    
  2. Make sure TypeScript is installed:

    npm install -g typescript ts-node
    
  3. Set up environment variables: Create a .env file in the root directory with your Bitbucket credentials:

    BITBUCKET_USERNAME=your-username
    BITBUCKET_PASSWORD=your-app-password
    

    Note: For Bitbucket Cloud, you need to use an "App Password" rather than your account password. Create one at: https://bitbucket.org/account/settings/app-passwords/

Running the Server

Start the Bitbucket MCP server:

npx ts-node src/index.ts

Or with Bun:

bun run dev

The server runs using a stdio transport, which means it expects to receive and send messages through standard input/output channels.

Using with Clients

To use this server from a client, see the example in example-client.ts. You can run the example with:

# First start the server in the background, then run the client
npx ts-node src/example-client.ts

Make sure your environment variables are set before running the client.

Example: Working with Pull Requests

// Connect to the MCP server
const client = new Client(
  {
    name: "example-bitbucket-client",
    version: "1.0.0",
  },
  {
    capabilities: {}
  }
);

const transport = new StdioClientTransport({
  command: "npx ts-node src/mcp.ts",
});

await client.connect(transport);

// Get open pull requests
const prResponse = await client.request(
  {
    method: "bitbucket/getPullRequests",
    params: {
      workspace: "your-workspace",
      repoSlug: "your-repo",
      state: "OPEN"
    }
  },
  BitbucketResultSchema
);

const pullRequests = prResponse.result;

// Create a new pull request
const newPrResponse = await client.request(
  {
    method: "bitbucket/createPullRequest",
    params: {
      workspace: "your-workspace",
      repoSlug: "your-repo",
      title: "My new pull request",
      source: {
        branch: {
          name: "feature-branch"
        }
      },
      destination: {
        branch: {
          name: "main"
        }
      },
      description: "This is a new feature implementation",
      close_source_branch: true
    }
  },
  BitbucketResultSchema
);

const newPullRequest = newPrResponse.result;

Integration with LLM Applications

This MCP server can be used with any MCP-compatible LLM application or framework. The client simply needs to:

  1. Connect to the server using the appropriate transport (stdio in this case)
  2. Make requests to the exposed Bitbucket API methods
  3. Handle the responses according to the application's needs

Security Considerations

The Bitbucket API requires authentication credentials, which are passed directly from the client to the server. Ensure that:

  1. Credentials are stored securely and never committed to version control
  2. The server is run in a secure environment
  3. Communication channels are secured appropriately for your use case

Further Reading

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Vibucket

How do I install Vibucket?

Run npx vibucket, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Vibucket safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Vibucket still maintained?

The last commit was a year ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.