mcpField
C
context-bridge

context-bridge

Local
github.com/jusspound-netizenDeveloper Tools0Updated today
Repository

About context-bridge

context-bridge is an MCP server that brings development context from tools such as Jira, Sentry, and GitHub Actions to a single endpoint for AI agents. It also provides a Slack status notification tool; the README identifies some data as mock data.

Key features

  1. 01Fetch Jira tickets by ID
  2. 02Retrieve Sentry issues
  3. 03Check GitHub Actions run status
  4. 04Send Slack status notifications

Use cases

  1. 01Let an AI agent check ticket progress
  2. 02Review alerts alongside CI status
  3. 03Send status updates through Slack

MCP support

context-bridge exposes development-data lookup and Slack notification tools as an MCP server. Its README describes adding the running server endpoint to AI environments such as Claude Code or Cursor.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "jusspound-netizen-context-bridge": {
      "command": "uvx",
      "args": [
        "context-bridge-mcp"
      ],
      "env": {
        "JIRA_BASE_URL": "<JIRA_BASE_URL>",
        "JIRA_EMAIL": "<JIRA_EMAIL>",
        "JIRA_API_TOKEN": "<JIRA_API_TOKEN>",
        "SENTRY_ORG_SLUG": "<SENTRY_ORG_SLUG>",
        "SENTRY_AUTH_TOKEN": "<SENTRY_AUTH_TOKEN>",
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<GITHUB_PERSONAL_ACCESS_TOKEN>"
      }
    }
  }
}
Run commanduvx context-bridge-mcp
Environment variables to set
JIRA_BASE_URLYour Jira instance URL (e.g., https://yourcompany.atlassian.net)
JIRA_EMAILYour Jira account email
JIRA_API_TOKENSecretYour Jira API token
SENTRY_ORG_SLUGYour Sentry organization slug
SENTRY_AUTH_TOKENSecretYour Sentry auth token
GITHUB_PERSONAL_ACCESS_TOKENSecretYour GitHub Personal Access Token

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypicontext-bridge-mcp1.0.0

Tools

3

Saved tool list · updated 4d ago

ParameterTypeRequiredDescription
ticket_idstringYes

Details

From the project README

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:

  1. pip install -r requirements.txt (or necessary dependencies)
  2. Set required environment variables (e.g., API keys for Jira/Sentry).
  3. 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:

  1. python server.py
  2. 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 NameDescriptionStatus
get_jira_ticketRetrieves mock Jira ticket data by ID.✅ Implemented
get_sentry_issuesRetrieves Sentry alerts.✅ Implemented
get_github_actions_runsChecks CI/CD status for a repo.✅ Implemented
send_slack_notificationSends status updates to Slack.✅ Implemented

License: MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.