Related Servers

Alternatives to .gitignore not found. The repository may be empty or the README is at the root only. Below is README.md raw content for analysis. Use it to propose GitHub recommendations, bugs, awesomeness, and a detailed report. Also, fix README.md formatting issues (like '## Overview' and '## Installation' headers missing line breaks). Provide a complete corrected README.md. Ensure no destructive operations, only safe recommendations and fixes. Include a safety note about no delete operations. Use the repo name 'bitbucket-mcp' in recommendations. Reference official npm package and CodeQL. Keep code blocks intact. Provide final JSON with name and description as requested. The name must be the MCP server name, not a person/maintainer/org. The description must say what the server enables and not restate the name. Max 2 sentences. Also, the README has a duplicate 'Pagination controls' line and truncated text at end. Mention in bugs. Also, missing 'createPullRequest' reviewers optional list, draft optional boolean. Ensure tool descriptions match. Also, the README says no DELETE operations but lists BITBUCKET_ENABLE_DANGEROUS for deletions, which contradicts 'no DELETE operations are used'. Flag as bug/inconsistency. Also, 'Checkout out' typo. Also, environment variables table: BITBUCKET_USERNAME and PASSWORD are 'Yes*' but token alternative. Clarify. Also, '1.' repeated numbering in troubleshooting. Also, 'Atlassian API Key' section says put API key in BITBUCKET_PASSWORD, not BITBUCKET_TOKEN, and use email as username. Good. Also, README says 'This is a safe and responsible package — no DELETE operations are used' but then BITBUCKET_ENABLE_DANGEROUS enables dangerous tools (e.g., deletions). Contradiction. Fix safety statement to reflect default safe mode and optional dangerous tools. Provide corrected README. Also, the repo URL in README badges points to MatanYemini/bitbucket-mcp, not QuynhChristou67177. Flag as bug: README references different GitHub repository. Also, npm badge and package name 'bitbucket-mcp'. Good. Also, the README's 'Available Tools' section is truncated at 'Pagination controls desc'. Need to complete or note truncation. Provide complete corrected README with all sections, no truncation. Also, ensure no DELETE operations by default; dangerous tools disabled by default. Provide safe recommendations. Provide awesomeness: good safety focus, CodeQL, NPX, Cursor integration, pagination. Provide GitHub recommendations: add .gitignore, LICENSE, CONTRIBUTING, issue templates, CI, tests, security policy, dependabot, release workflow, npm publish automation, README badges, correct repo links, add examples, add tool schema docs, add changelog, add support for Bitbucket Server APIs (README says Cloud and Server but only Cloud examples). Add server support details. Add rate limiting/retry. Add logging config docs. Add token alternative docs. Add Docker. Add tests. Add mcp inspector. Add versioning. Add semantic release. Add code of conduct. Add FAQ. Add troubleshooting for 403, 404, rate limits. Add sample Cursor config for token auth. Add environment variable validation. Add health check. Add graceful shutdown. Add telemetry opt-in? No. Add security note about app passwords least privilege. Add note about no DELETE by default. Add note about CodeQL. Add note about npm provenance. Add note about package integrity. Add note about pinning versions. Add note about npx -y risk. Add note about supply chain. Add note about audit. Add note about license MIT. Add note about contributing. Add note about issues. Add note about discussions. Add note about roadmap. Add note about supported Bitbucket versions. Add note about Server API differences. Add note about authentication for Server (PAT vs app password). Add note about SSL verification. Add note about proxy. Add note about custom CA. Add note about timeouts. Add note about pagination cap 1000. Add note about all=true safety cap. Add note about limit deprecated. Add note about pagelen cap 100. Add note about page 1-based. Add note about listRepositories name filter partial match. Add note about getPullRequests state enum. Add note about createPullRequest reviewers usernames, draft boolean. Add note about getPullRequest pagination controls (probably copy-paste error; getPullRequest shouldn't have pagination). Flag as bug: getPullRequest includes pagination controls, likely copy-paste from list tools. Also duplicate line. Also truncated. Provide corrected README with getPullRequest without pagination. Also, README says 'Pagination controls described in [Pagination](#pagination)' twice for getPullRequest. Remove. Also, the README is truncated at 'Pagination controls desc'. Complete the Available Tools section with remaining tools? The README only shows listRepositories, getRepository, getPullRequests, createPullRequest, getPullRequest. The overview says 'And more...' but no more listed. Mention incomplete tool list. Provide corrected README with a note that more tools may exist in code, but README should list all. Since we only have README, we can't invent tools. Provide a placeholder 'Additional tools may be documented in the source code' or 'See source for full list'. But better to keep only documented tools and note incomplete. Provide corrected README with complete sections up to getPullRequest, remove duplicate/truncated lines, and add a note that the list is incomplete and should be updated. Also, fix 'Checkout out' to 'Check out'. Fix '1.' numbering in troubleshooting to use proper ordered list. Fix 'Yes*' clarify. Fix safety statement. Fix repo links to QuynhChristou67177? But README badges point to MatanYemini. Since the user says GitHub names the repository 'bitbucket-mcp' and describes it as..., but the README references MatanYemini. The name must be the MCP server name, not a person/maintainer/org. The MCP server name is 'bitbucket-mcp' or 'Bitbucket MCP'. The description must say what the server enables. So final JSON: name: 'Bitbucket MCP'? The repository publishes 'bitbucket-mcp' npm package. The README title '# Bitbucket MCP'. The name must name the MCP server the repository publishes. The npm package is 'bitbucket-mcp'. The MCP server name could be 'Bitbucket MCP' or 'bitbucket-mcp'. The user says 'Respond with a name and no more than 2 sentences long description of the MCP server. The name must name the MCP server the repository publishes – never a person, maintainer, or organization the README credits.' The README credits MatanYemini in badges. So don't use MatanYemini. Use 'Bitbucket MCP' or 'bitbucket-mcp'. The repository name is 'bitbucket-mcp'. The npm package is 'bitbucket-mcp'. The MCP server name likely 'bitbucket-mcp'. But the title is 'Bitbucket MCP'. The user asks 'Evaluate the first 10,000 characters of README.md... Respond with a name and no more than 2 sentences long description of the MCP server.' So final JSON should have name and description. Name: 'Bitbucket MCP' (the server) or 'bitbucket-mcp' (package). The description: 'Enables AI assistants to interact with Bitbucket Cloud and Server APIs for listing and retrieving repositories, fetching and creating pull requests, and managing Bitbucket resources through the Model Context Protocol.' That's one sentence. Must not restate the name. Good. But the description must say what the server enables. Yes. Max 2 sentences. Good. Also, the user asked to 'Evaluate' and 'Respond with a name and no more than 2 sentences long description' and 'Reply with a JSON object that has properties name and description'. So final answer should be only JSON? The user says 'Reply with a JSON object that has properties