Skip to main content
Glama
Sign In
Context Bridge

Context Bridge

by jusspound-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Context Bridge

Glama MCP Server M8ven Score Context Bridge MCP server

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.

Related MCP server: Aurea Orchestrator MCP

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

Fetches a Jira ticket by issue key via the Jira REST API.

Yes Implemented

get_sentry_issues

Lists unresolved Sentry issues by project slug.

Yes Implemented

get_github_actions_runs

Checks CI/CD status for a repo.

Yes Implemented

License: MIT

Related projects

Ready-to-use Agent Skills

Want your AI agent to use these tools automatically? Get the Dev Context Connector skill on Agensi. It includes the exact setup instructions and configuration templates for Claude Code, Cursor, and other MCP clients.

Get Dev Context Connector on Agensi

Available Tools

3 tools
get_github_actions_runsA
Read-only

Lists recent GitHub Actions workflow runs for a repository (owner/repo). Returns JSON array with run id, name, status, conclusion, head_branch, and html_url. Optional limit (default 5). Requires GITHUB_PERSONAL_ACCESS_TOKEN with actions:read scope.

Inputs: repo (required), owner (required), limit. Returns: result

get_jira_ticketA
Read-onlyIdempotent

Retrieves a Jira ticket by its issue key (e.g. 'PROJ-123'). Returns JSON with id, summary, status, assignee, and description fields. Requires JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN environment variables.

Inputs: ticket_id (required). Returns: result

get_sentry_issuesA
Read-only

Lists recent unresolved issues from a Sentry project by project slug. Returns JSON array with issue id, title, culprit, count, and first_seen. Optional limit (default 5). Requires SENTRY_ORG_SLUG and SENTRY_AUTH_TOKEN environment variables.

Inputs: project_slug (required), limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a completely distinct external service (Sentry, Jira, GitHub Actions), so there is no plausible overlap or misselection risk.

    Naming Consistency4/5

    All tools follow a clear get_<service>_<resource> pattern, making intent predictable. Minor inconsistency: get_sentry_issues and get_github_actions_runs are plural while get_jira_ticket is singular, but this reflects the underlying resource semantics.

    Tool Count4/5

    Three tools is thin but defensible for a read-only context aggregation server where each tool maps to one integration. It is slightly under-scoped rather than bloated.

    Completeness3/5

    The surface only supports listing/fetching at one level: no Sentry issue detail, no GitHub run or PR detail, and no Jira search or comment retrieval. Core 'pull context' use cases work, but agents hitting detail or filtering needs will hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers