This MCP server collection provides four production-ready servers that integrate with major development and project management platforms: GitHub, Bitbucket, GitLab, and Jira. Each server exposes a set of MCP tools that allow AI assistants to read and write code, manage issues, handle pull/merge requests, and perform repository operations via platform-specific APIs and Git CLI integrations. To use them, run the individual server(s) and configure your MCP client to point to the server entry points using the command and environment variables shown in the mcp_config. Once launched, your MCP client can invoke the registered tools for each platform by referencing the corresponding server and providing authentication tokens or API credentials through environment variables.

You can compose an MCP client configuration that includes the four servers, enabling cross-platform workflows such as creating a GitHub issue while cross-referencing a Jira ticket, or automating repository maintenance tasks across GitHub and GitLab. Each server is designed with modular tooling, type-safe validation, and robust logging to help AI agents execute tasks reliably within its platform.

Prerequisites:

• Node.js v18.0.0 or higher
• Git
• Access tokens or API credentials for each platform (as described in authentication guidance)

Installation steps:

1. Clone the MCP Servers collection: git clone https://github.com/sameerbudhiraja-mcp_servers.git
2. Navigate to the collection root: cd mcp_servers
3. Install dependencies for all servers (run in parallel or per server): npm install
4. Configure environment variables for each server by copying the example files and editing them: cp github/.env.example github/.env

   edit github/.env with your GitHub token and settings

   cp bitbucket/.env.example bitbucket/.env

   edit bitbucket/.env with your Bitbucket credentials

   cp gitlab/.env.example gitlab/.env

   edit gitlab/.env with your GitLab token

   cp jira/.env.example jira/.env

   edit jira/.env with your Jira credentials

5. Start a specific server (example for GitHub): cd github npm start
6. Repeat for other servers as needed. To run multiple servers concurrently, start each in separate terminal sessions or use a process manager like pm2 or docker as appropriate.

Tips and considerations:

• Ensure the environment variables are securely stored and not committed to version control.
• Logs are rotated daily; adjust LOG_LEVEL and LOGGING_ENABLED as needed for debugging and performance.
• If you enable multiple servers, your MCP client configuration should reference absolute paths to each server's entry file, as shown in the example mcp_config.
• For Bitbucket and Jira, API tokens may require specific scopes; verify the required permissions in their respective authentication guides.
• The architecture emphasizes modular tool registration; if you add a new tool for any platform, follow the same pattern: update endpoints, define the schema with Zod, and implement the service logic in the appropriate folder.
• When running behind a proxy or in Docker/Kubernetes, ensure network egress is allowed to the respective platform APIs and that credentials remain secret.