Context Bridge
Context Bridge - one MCP endpoint for all your dev tools
Problem:
- Tool sprawl across Jira, Sentry, GitHub, and CI systems.
- Context fragmentation makes it hard for AI agents to operate across tools.
- AI agents are currently blind to critical development context (Jira tickets, Sentry alerts, CI status).
Setup:
pip install -r requirements.txt(or necessary dependencies)- Set required environment variables (e.g., API keys for Jira/Sentry).
- Add the running MCP server endpoint to your AI environment (e.g., Claude Code or Cursor) as a custom MCP server.
Quick Start
To run the server:
python server.py- Ensure required environment variables are set.
Example
A sample response from get_jira_ticket:
{"id": "PROJ-123", "summary": "Fix login bug", "status": "In Progress"}
Tools:
| Tool Name | Description | Status |
|---|---|---|
get_jira_ticket |
Retrieves mock Jira ticket data by ID. | ✅ Implemented |
get_sentry_issues |
Retrieves Sentry alerts. | ✅ Implemented |
get_github_actions_runs |
Checks CI/CD status for a repo. | ✅ Implemented |
send_slack_notification |
Sends status updates to Slack. | ✅ Implemented |
License: MIT
1 maintainer
Metadata
1 maintainer
Release files for context-bridge-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| context_bridge_mcp-1.0.0.tar.gz | 3.3 kB | Without provenance | Details for context_bridge_mcp-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| context_bridge_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for context_bridge_mcp-1.0.0-py3-none-any.whl |
Total release size: 6.9 kB
Release files / context_bridge_mcp-1.0.0.tar.gz
| Download URL | context_bridge_mcp-1.0.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96303c8c6d739eff40e3f83daf27ab9a8dadb2ae70ebb123fc79849a69316bf5
|
|
BLAKE2b-256 checksum How to use checksums |
825bfd99c8de58b279b898e44a7bc1fdf0f6c404605641252b34532b298ed551
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.2
|
Release files / context_bridge_mcp-1.0.0-py3-none-any.whl
| Download URL | context_bridge_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4486e898be556fd6d1a2aeeb71fb0eb5a7148681a90dba992b231556cc51d391
|
|
BLAKE2b-256 checksum How to use checksums |
0aaa77dec1cf749557ae89d653e82b766e4d2faaca1152fed37b87597fa61449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.2
|
Security for context-bridge-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
