Claude MarketplacesSubmit

Rebar

navapbc/rebar

This is an event-sourced ticket system that syncs with Jira through a reconciler pattern, letting Claude interact with your issue tracking through MCP. The event sourcing architecture means all ticket changes are stored as events rather than just current state, which is useful when you need audit trails or want to replay history. You'd reach for this when you want Claude to query, create, or update tickets while maintaining a local event log that reconciles with Jira. The stdio transport makes it straightforward to wire up locally. Good fit if you're already running Jira but want an event-sourced layer on top with LLM access baked in.

GitHub stars: 5
tools: 8
transport: STDIO
env vars: 24
last updated: Nov 12, 2026

Tools

8 tools

Public tool metadata for what this MCP can expose to an agent.

bridge_previewExplicit MCP bridge tool for previewing Jira sync.

Explicit MCP bridge tool for previewing Jira sync.

No parameter schema in public metadata yet.

bridge_runExplicit MCP bridge tool for running Jira sync; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

Explicit MCP bridge tool for running Jira sync; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

No parameter schema in public metadata yet.

bridge_syncExplicit MCP bridge tool for syncing with Jira; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

Explicit MCP bridge tool for syncing with Jira; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

No parameter schema in public metadata yet.

bridge_statusExplicit MCP bridge tool for checking Jira bridge status.

Explicit MCP bridge tool for checking Jira bridge status.

No parameter schema in public metadata yet.

bridge_pauseExplicit MCP bridge tool for pausing the Jira bridge; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

Explicit MCP bridge tool for pausing the Jira bridge; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

No parameter schema in public metadata yet.

bridge_resumeExplicit MCP bridge tool for resuming the Jira bridge; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

Explicit MCP bridge tool for resuming the Jira bridge; mutating and requires REBAR_MCP_ALLOW_JIRA_SYNC=1.

No parameter schema in public metadata yet.

bridge_check_accessExplicit MCP bridge tool for checking Jira access.

Explicit MCP bridge tool for checking Jira access.

No parameter schema in public metadata yet.

bridge_fsckExplicit MCP bridge tool for checking bridge consistency.

Explicit MCP bridge tool for checking bridge consistency.

No parameter schema in public metadata yet.

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly

Agent CaffeineSponsoredClose your lid, come back to finished work

SnugSponsoredThe clipboard manager for the AI era Promote your product hereReach 125k+ visitors monthly

WaxSponsoredBlock anything with supervision, without erasing your iPhone Promote your product hereReach 125k+ visitors monthly

knobsSponsoredSee your site on any phone, any day, in any language

Configuration

REBAR_ROOT

Path to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).

REBAR_MCP_READONLY

Set to 1 to expose only the read tools (no write/mutation tools).

REBAR_MCP_ALLOW_LLM

Set to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.

REBAR_MCP_DEDUP

In-flight de-duplication of the long-running gate tools (review_plan / verify_completion): a concurrent duplicate call for the same ticket+basis attaches to the running gate instead of launching a second billable LLM pass. On by default; set to 0 to disable (kill-switch).

REBAR_MCP_ALLOW_JIRA_SYNC

Set to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.

REBAR_MCP_TRANSPORT

Transport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).

REBAR_MCP_HTTP_HOST

Bind host for the Streamable-HTTP transport (default 127.0.0.1).

REBAR_MCP_HTTP_PORT

Bind port for the Streamable-HTTP transport (1-65535; default 8000).

REBAR_MCP_HTTP_PATH

URL path the Streamable-HTTP transport serves on (default /mcp).

REBAR_MCP_HTTP_ALLOWED_HOSTS

Comma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.

REBAR_MCP_HTTP_ALLOWED_ORIGINS

Comma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.

REBAR_MCP_HTTP_TLS_AT_EDGE

Set to 1 to acknowledge TLS is terminated at the edge; required to bind the Streamable-HTTP transport to a non-loopback host.

REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP

Set to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.

REBAR_MCP_AUTH_ENABLED

Set to 1 to enable MCP authentication (the composite token verifier + Resource-Server wiring); off by default.

REBAR_MCP_AUTH_STRATEGIES

Comma-separated, ordered list of token-verifier strategies to compose (closed set: static, jwt, introspection, proxy, custom).

REBAR_MCP_AUTH_ISSUER_URL

OAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.

REBAR_MCP_AUTH_RESOURCE_SERVER_URL

The single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.

REBAR_MCP_AUTH_REQUIRED_SCOPES

Comma-separated scopes a caller must hold; the SDK returns 403 insufficient_scope when a principal lacks one.

REBAR_MCP_AUTH_STATIC_TOKENS_FILE

Path to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).

REBAR_MCP_AUTH_JWT_JWKS_URI

HTTPS JWKS endpoint the `jwt` verifier fetches signing keys from (an OIDC provider's .well-known/jwks.json).

REBAR_MCP_AUTH_JWT_ISSUER

Expected `iss` claim for the `jwt` verifier; falls back to REBAR_MCP_AUTH_ISSUER_URL when unset.

REBAR_MCP_AUTH_JWT_ALGORITHMS

Comma-separated PINNED, asymmetric-only JWS algorithms for the `jwt` verifier (default RS256,ES256); a symmetric algorithm on a JWKS source is refused.

REBAR_MCP_AUTH_JWT_LEEWAY

Clock-skew leeway in seconds applied to exp/nbf validation by the `jwt` verifier (default 60).

REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN

Minimum seconds between JWKS refetches triggered by an unknown key id (the concurrency-safe flood guard; default 30).

Readme

rebar

An event-sourced, git-backed ticket store + Jira reconciler built for agent swarms — one store, exposed as a Python library, a CLI, and an MCP server.

rebar's core loop: rebar ready → rebar claim → rebar transition … closed

View the full README on GitHub

Details

Repository: github.com/navapbc/rebar
Category: Developer Tools
Package: nava-rebar
Transport: STDIO
Registry: MCP registry, active

Related Developer Tools MCP servers

1

glim.shglim-sh/glim-mcpGive your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.4stars

2

kObsidianbezata/kobsidianFilesystem-first MCP for Obsidian — an LLM-maintained wiki inspired by Karpathy's LLM Wiki.3stars

3

Megalinterdownatthebottomofthemolehole/megalinter-mcpMCP server for running Ox Security MegaLinter via mega-linter-runner3stars

4

Ssh Client Mcp Serverjordanburke/ssh-client-mcp-serverMCP server for executing shell commands on remote hosts via SSH.3stars

5

Aman Amith Shastry Scientific Computation Mcpaman-amith-shastry/scientific_computation_mcpThis MCP server enables users to perform scientific computations regarding linear algebra and vect…2stars

6

Contextforge Mcpalfredoizdev/contextforge-mcpPersistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.2stars