Jira, Confluence, Bitbucket and Jenkins MCP
Sberworks MCP
A local stdio MCP server for self-hosted Jira, Confluence, Bitbucket Server and Jenkins, with mTLS support and write tools disabled by default
- 1 ★ on the repository
- Last commit
Extended access
Why this level
- Write tools create issues, pages, pull requests and trigger Jenkins builds, but are disabled by default
- It stores a corporate mTLS certificate and password in .env on disk
Install
- Works in
Manual install
uv run sberworks-mcp init && uv run sberworks-mcp doctorCreates a local .env and validates the setup before the first connection.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Write tools create issues, pages, pull requests and trigger Jenkins builds, but are disabled by default
- It stores a corporate mTLS certificate and password in .env on disk
This is third-party code. Review the repository files before installing.
What it does
A Python server gives unified MCP access to four corporate systems: Jira (search, issues, comments, attachments, status transitions, Zephyr test cycles), Confluence (search, pages, attachments, page creation and updates), Bitbucket Server or Data Center (repositories, pull requests, files, diffs) and Jenkins (jobs, builds, console output, artifacts, queue). It has a CLI: init creates a local .env, doctor validates the setup, config-snippet generates a ready config for Claude, Codex or VS Code with absolute paths. It supports mTLS via a P12 client certificate and SAML login for Jenkins. Write tools (creating issues, pages, pull requests, triggering builds) are disabled by default behind the SBERWORKS_MCP_ENABLE_WRITES flag.
Who it is for. For developers and QA engineers at companies running self-hosted Jira, Confluence, Bitbucket and Jenkins who want one MCP server for the whole stack.
Good fit when
- You need unified MCP access to self-hosted Jira, Confluence, Bitbucket Server and Jenkins at once
- You need support for a corporate mTLS certificate or SAML login into Jenkins
- You want to safely try the read tools before turning on writes to Jira and Confluence
Not a fit when
- You need only cloud Atlassian services with no self-hosted server: the config targets self-hosted Server and Data Center
- You need Jenkins file parameters or Jenkins administration: not supported
Example request
Find open Jira issues for the project and show recent builds of the Folder/Multibranch/main job in JenkinsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
JIRA_BASE_URLrequired- Self-hosted Jira base URL
AUTH_USERNAMErequired- Login for Jira, Confluence and Bitbucket
AUTH_PASSWORDrequired, secret- Password or token for Jira, Confluence and Bitbucket
SBERWORKS_MCP_ENABLE_WRITES- Defaults to false; enables write tools and Jenkins build triggers
Limitations
Despite the name, the server has nothing to do with Sberbank's banking API: it is an MCP for Jira, Confluence, Bitbucket and Jenkins, and the name and the jenkins-ci example domain in the README point to an internal corporate DevOps portal. The repository has no license. It requires your own self-hosted instances with base URLs for every system; there are no ready-made credentials.
How to disable. Remove the sberworks-mcp entry from your MCP client config and delete the .env file with credentials and certificates.
FAQ
What does this have to do with Sberbank?
Nothing: it is an MCP for Jira, Confluence, Bitbucket and Jenkins; the name and the example domain in the README point to an internal company portal, not a banking API.
How do I enable creating issues and pull requests?
Set SBERWORKS_MCP_ENABLE_WRITES=true in .env or as an environment variable; only read tools are available by default.
Discussion
No questions or reviews yet.
Related
MCP serversA Bitbucket Cloud MCP server with six generic tools that reach any repository or pull request REST API path
A plugin that turns Jenkins into an MCP server so an agent can inspect jobs and build logs, trigger builds and read test results.
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
A Node.js manager for MCP servers: it starts local servers, connects remote ones and gives a client one address, with a REST API for control
jirac runs Jira from the terminal: a TUI, a JQL builder, bulk operations and an MCP server for agents in one binary.
A local agent runtime and MCP gateway with 298 tools: files, Git, processes, Chrome browser, Windows and Office
README in short
The README describes installing via uv or venv and pip, the init, doctor and config-snippet commands for generating Claude, Codex and VS Code configs with absolute paths, running in Docker with mounted certificates, required environment variables for the four systems, the full tool list per system plus Zephyr test cycles, MCP resources under the jira://, confluence://, bitbucket:// and zephyr:// schemes, and a troubleshooting section with Claude Desktop log locations.