io.github.navapbc/rebarproductivity

rebar

Verified · yesterday

Event-sourced ticket system with a Jira reconciler, exposed as an MCP server.

Install

claude mcp add rebar -- uvx nava-rebar

Requires: REBAR_ROOT, REBAR_MCP_READONLY, REBAR_MCP_ALLOW_LLM, REBAR_MCP_ALLOW_JIRA_SYNC, REBAR_MCP_TRANSPORT, REBAR_MCP_HTTP_HOST, REBAR_MCP_HTTP_PORT, REBAR_MCP_HTTP_PATH, REBAR_MCP_HTTP_ALLOWED_HOSTS, REBAR_MCP_HTTP_ALLOWED_ORIGINS, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP, REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_ISSUER_URL, REBAR_MCP_AUTH_RESOURCE_SERVER_URL, REBAR_MCP_AUTH_REQUIRED_SCOPES, REBAR_MCP_AUTH_STATIC_TOKENS_FILE, REBAR_MCP_AUTH_JWT_JWKS_URI, REBAR_MCP_AUTH_JWT_ISSUER, REBAR_MCP_AUTH_JWT_ALGORITHMS, REBAR_MCP_AUTH_JWT_LEEWAY, REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN, REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT, REBAR_MCP_AUTH_JWT_EXPECTED_TYP, REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOST, REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOST, REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD, REBAR_MCP_AUTH_PROXY_SECRET_ENV, REBAR_MCP_AUTH_PROXY_SECRET_HEADER, REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER, REBAR_MCP_AUTH_PROXY_SCOPES, REBAR_MCP_AUTH_CUSTOM_IMPORT

Our take

This server presents an event-sourced ticketing system with Jira reconciliation, suggesting a workflow layer between internal issue tracking and Jira. It is for teams that want structured ticket state and synchronization rather than a generic task manager. The concept is credible but specialized, and with no visible usage or maintenance indicators it looks like a focused infrastructure component rather than a broadly adopted MCP server.

reviewed by hand · 2026-07-26

Something wrong or dead here? Report it