What it does
Event-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server.
- Connects Runs on your computer
- Account or key Needs REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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 · 2 settings to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP)
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 9/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 21/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Rebar. Follow https://mcp.popnx.com/i/navapbc-rebar.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Rebar for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "rebar": { "command": "uvx", "args": [ "nava-rebar" ], "env": { "REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value", "REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value", "REBAR_MCP_AUTH_ENABLED": "your-value", "REBAR_MCP_AUTH_STRATEGIES": "your-value", "REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value", "REBAR_MCP_AUTH_JWT_ISSUER": "your-value", "REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value", "REBAR_MCP_AUTH_JWT_LEEWAY": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_SCOPES": "your-value", "REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Rebar tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Sign up and create a Rebar key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
REBAR_MCP_HTTP_TLS_AT_EDGESet 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_HTTPSet to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.
Descriptions are as written by the maker.
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "rebar": { "command": "uvx", "args": [ "nava-rebar" ], "env": { "REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value", "REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value", "REBAR_MCP_AUTH_ENABLED": "your-value", "REBAR_MCP_AUTH_STRATEGIES": "your-value", "REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value", "REBAR_MCP_AUTH_JWT_ISSUER": "your-value", "REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value", "REBAR_MCP_AUTH_JWT_LEEWAY": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_SCOPES": "your-value", "REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value" } } } }Paste the key only into the app’s field, never into a chat or to anyone
Quit Claude and open it again
Try it
Use Rebar and tell me what you can do for me, then show me one thing✓ If Claude says it is using Rebar or shows a Rebar tool in the answer, you are connected
17 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
REBAR_ROOTPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).REBAR_MCP_READONLYSet to 1 to expose only the read tools (no write/mutation tools).REBAR_MCP_ALLOW_LLMSet to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.REBAR_MCP_DEDUPIn-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 se…REBAR_MCP_ALLOW_JIRA_SYNCSet to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.REBAR_MCP_TRANSPORTTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).REBAR_MCP_HTTP_HOSTBind host for the Streamable-HTTP transport (default 127.0.0.1).REBAR_MCP_HTTP_PORTBind port for the Streamable-HTTP transport (1-65535; default 8000).REBAR_MCP_HTTP_PATHURL path the Streamable-HTTP transport serves on (default /mcp).REBAR_MCP_HTTP_ALLOWED_HOSTSComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_ALLOWED_ORIGINSComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_AUTH_ISSUER_URLOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.REBAR_MCP_AUTH_RESOURCE_SERVER_URLThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.REBAR_MCP_AUTH_STATIC_TOKENS_FILEPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).REBAR_MCP_AUTH_JWT_EXPECTED_TYPWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Rebar yet
Rebar runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Rebar
- You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
- You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
- You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Rebar for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user rebar --env REBAR_MCP_HTTP_TLS_AT_EDGE=your-value --env REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP=your-value --env REBAR_MCP_AUTH_ENABLED=your-value --env REBAR_MCP_AUTH_STRATEGIES=your-value --env REBAR_MCP_AUTH_REQUIRED_SCOPES=your-value --env REBAR_MCP_AUTH_JWT_JWKS_URI=your-value --env REBAR_MCP_AUTH_JWT_ISSUER=your-value --env REBAR_MCP_AUTH_JWT_ALGORITHMS=your-value --env REBAR_MCP_AUTH_JWT_LEEWAY=your-value --env REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN=your-value --env REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_ENV=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_SCOPES=your-value --env REBAR_MCP_AUTH_CUSTOM_IMPORT=your-value -- uvx nava-rebar 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Rebar tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Sign up and create a Rebar key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
REBAR_MCP_HTTP_TLS_AT_EDGESet 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_HTTPSet to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.
Descriptions are as written by the maker.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user rebar --env REBAR_MCP_HTTP_TLS_AT_EDGE=your-value --env REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP=your-value --env REBAR_MCP_AUTH_ENABLED=your-value --env REBAR_MCP_AUTH_STRATEGIES=your-value --env REBAR_MCP_AUTH_REQUIRED_SCOPES=your-value --env REBAR_MCP_AUTH_JWT_JWKS_URI=your-value --env REBAR_MCP_AUTH_JWT_ISSUER=your-value --env REBAR_MCP_AUTH_JWT_ALGORITHMS=your-value --env REBAR_MCP_AUTH_JWT_LEEWAY=your-value --env REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN=your-value --env REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_ENV=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_SCOPES=your-value --env REBAR_MCP_AUTH_CUSTOM_IMPORT=your-value -- uvx nava-rebarReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
Type /mcp in Claude Code
You should see Rebar listed as connected
Try it
Use Rebar and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Rebar or shows a Rebar tool in the answer, you are connected
17 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
REBAR_ROOTPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).REBAR_MCP_READONLYSet to 1 to expose only the read tools (no write/mutation tools).REBAR_MCP_ALLOW_LLMSet to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.REBAR_MCP_DEDUPIn-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 se…REBAR_MCP_ALLOW_JIRA_SYNCSet to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.REBAR_MCP_TRANSPORTTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).REBAR_MCP_HTTP_HOSTBind host for the Streamable-HTTP transport (default 127.0.0.1).REBAR_MCP_HTTP_PORTBind port for the Streamable-HTTP transport (1-65535; default 8000).REBAR_MCP_HTTP_PATHURL path the Streamable-HTTP transport serves on (default /mcp).REBAR_MCP_HTTP_ALLOWED_HOSTSComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_ALLOWED_ORIGINSComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_AUTH_ISSUER_URLOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.REBAR_MCP_AUTH_RESOURCE_SERVER_URLThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.REBAR_MCP_AUTH_STATIC_TOKENS_FILEPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).REBAR_MCP_AUTH_JWT_EXPECTED_TYPWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Rebar for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "rebar": { "command": "uvx", "args": [ "nava-rebar" ], "env": { "REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value", "REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value", "REBAR_MCP_AUTH_ENABLED": "your-value", "REBAR_MCP_AUTH_STRATEGIES": "your-value", "REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value", "REBAR_MCP_AUTH_JWT_ISSUER": "your-value", "REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value", "REBAR_MCP_AUTH_JWT_LEEWAY": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_SCOPES": "your-value", "REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Rebar tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Sign up and create a Rebar key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
REBAR_MCP_HTTP_TLS_AT_EDGESet 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_HTTPSet to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.
Descriptions are as written by the maker.
Fill in your key
In the Rebar settings, REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in Cursor in Agent mode
Try it
Use Rebar and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Rebar or shows a Rebar tool in the answer, you are connected
17 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
REBAR_ROOTPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).REBAR_MCP_READONLYSet to 1 to expose only the read tools (no write/mutation tools).REBAR_MCP_ALLOW_LLMSet to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.REBAR_MCP_DEDUPIn-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 se…REBAR_MCP_ALLOW_JIRA_SYNCSet to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.REBAR_MCP_TRANSPORTTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).REBAR_MCP_HTTP_HOSTBind host for the Streamable-HTTP transport (default 127.0.0.1).REBAR_MCP_HTTP_PORTBind port for the Streamable-HTTP transport (1-65535; default 8000).REBAR_MCP_HTTP_PATHURL path the Streamable-HTTP transport serves on (default /mcp).REBAR_MCP_HTTP_ALLOWED_HOSTSComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_ALLOWED_ORIGINSComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_AUTH_ISSUER_URLOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.REBAR_MCP_AUTH_RESOURCE_SERVER_URLThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.REBAR_MCP_AUTH_STATIC_TOKENS_FILEPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).REBAR_MCP_AUTH_JWT_EXPECTED_TYPWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.
Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Rebar key (create it on the maker’s site) · 2 setting(s) to fill in (REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP) · Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Rebar for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "rebar": { "type": "stdio", "command": "uvx", "args": [ "nava-rebar" ], "env": { "REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value", "REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value", "REBAR_MCP_AUTH_ENABLED": "your-value", "REBAR_MCP_AUTH_STRATEGIES": "your-value", "REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value", "REBAR_MCP_AUTH_JWT_ISSUER": "your-value", "REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value", "REBAR_MCP_AUTH_JWT_LEEWAY": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value", "REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value", "REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value", "REBAR_MCP_AUTH_PROXY_SCOPES": "your-value", "REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Rebar tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Sign up and create a Rebar key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
REBAR_MCP_HTTP_TLS_AT_EDGESet 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_HTTPSet to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off.
Descriptions are as written by the maker.
Fill in your key
In the Rebar settings, REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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, REBAR_MCP_HTTP_TLS_AT_EDGE, REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in VS Code in Agent mode
Try it
Use Rebar and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Rebar or shows a Rebar tool in the answer, you are connected
17 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
REBAR_ROOTPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).REBAR_MCP_READONLYSet to 1 to expose only the read tools (no write/mutation tools).REBAR_MCP_ALLOW_LLMSet to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.REBAR_MCP_DEDUPIn-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 se…REBAR_MCP_ALLOW_JIRA_SYNCSet to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.REBAR_MCP_TRANSPORTTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).REBAR_MCP_HTTP_HOSTBind host for the Streamable-HTTP transport (default 127.0.0.1).REBAR_MCP_HTTP_PORTBind port for the Streamable-HTTP transport (1-65535; default 8000).REBAR_MCP_HTTP_PATHURL path the Streamable-HTTP transport serves on (default /mcp).REBAR_MCP_HTTP_ALLOWED_HOSTSComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_ALLOWED_ORIGINSComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_AUTH_ISSUER_URLOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.REBAR_MCP_AUTH_RESOURCE_SERVER_URLThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.REBAR_MCP_AUTH_STATIC_TOKENS_FILEPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).REBAR_MCP_AUTH_JWT_EXPECTED_TYPWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.
Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user rebar --env REBAR_MCP_HTTP_TLS_AT_EDGE=your-value --env REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP=your-value --env REBAR_MCP_AUTH_ENABLED=your-value --env REBAR_MCP_AUTH_STRATEGIES=your-value --env REBAR_MCP_AUTH_REQUIRED_SCOPES=your-value --env REBAR_MCP_AUTH_JWT_JWKS_URI=your-value --env REBAR_MCP_AUTH_JWT_ISSUER=your-value --env REBAR_MCP_AUTH_JWT_ALGORITHMS=your-value --env REBAR_MCP_AUTH_JWT_LEEWAY=your-value --env REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN=your-value --env REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID=your-value --env REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV=your-value --env REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_ENV=your-value --env REBAR_MCP_AUTH_PROXY_SECRET_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER=your-value --env REBAR_MCP_AUTH_PROXY_SCOPES=your-value --env REBAR_MCP_AUTH_CUSTOM_IMPORT=your-value -- uvx nava-rebarClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
],
"env": {
"REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value",
"REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value",
"REBAR_MCP_AUTH_ENABLED": "your-value",
"REBAR_MCP_AUTH_STRATEGIES": "your-value",
"REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value",
"REBAR_MCP_AUTH_JWT_ISSUER": "your-value",
"REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value",
"REBAR_MCP_AUTH_JWT_LEEWAY": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_SCOPES": "your-value",
"REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
],
"env": {
"REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value",
"REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value",
"REBAR_MCP_AUTH_ENABLED": "your-value",
"REBAR_MCP_AUTH_STRATEGIES": "your-value",
"REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value",
"REBAR_MCP_AUTH_JWT_ISSUER": "your-value",
"REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value",
"REBAR_MCP_AUTH_JWT_LEEWAY": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_SCOPES": "your-value",
"REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"rebar": {
"type": "stdio",
"command": "uvx",
"args": [
"nava-rebar"
],
"env": {
"REBAR_MCP_HTTP_TLS_AT_EDGE": "your-value",
"REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP": "your-value",
"REBAR_MCP_AUTH_ENABLED": "your-value",
"REBAR_MCP_AUTH_STRATEGIES": "your-value",
"REBAR_MCP_AUTH_REQUIRED_SCOPES": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_URI": "your-value",
"REBAR_MCP_AUTH_JWT_ISSUER": "your-value",
"REBAR_MCP_AUTH_JWT_ALGORITHMS": "your-value",
"REBAR_MCP_AUTH_JWT_LEEWAY": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN": "your-value",
"REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_ENV": "your-value",
"REBAR_MCP_AUTH_PROXY_SECRET_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER": "your-value",
"REBAR_MCP_AUTH_PROXY_SCOPES": "your-value",
"REBAR_MCP_AUTH_CUSTOM_IMPORT": "your-value"
}
}
}
}Values you fill in
REBAR_ROOTenvPath to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir).REBAR_MCP_READONLYenvSet to 1 to expose only the read tools (no write/mutation tools).REBAR_MCP_ALLOW_LLMenvSet to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default.REBAR_MCP_DEDUPenvIn-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 se…REBAR_MCP_ALLOW_JIRA_SYNCenvSet to 1 to allow bridge_sync to perform live (mutating) Jira sync; otherwise bridge_sync uses dry-run behavior.REBAR_MCP_TRANSPORTenvTransport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport).REBAR_MCP_HTTP_HOSTenvBind host for the Streamable-HTTP transport (default 127.0.0.1).REBAR_MCP_HTTP_PORTenvBind port for the Streamable-HTTP transport (1-65535; default 8000).REBAR_MCP_HTTP_PATHenvURL path the Streamable-HTTP transport serves on (default /mcp).REBAR_MCP_HTTP_ALLOWED_HOSTSenvComma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_ALLOWED_ORIGINSenvComma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback.REBAR_MCP_HTTP_TLS_AT_EDGErequired envSet 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_HTTPrequired envSet 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_ENABLEDsecret required envSet to 1 to enable MCP authentication (the composite token verifier + Resource-Server wiring); off by default.REBAR_MCP_AUTH_STRATEGIESsecret required envComma-separated, ordered list of token-verifier strategies to compose (closed set: static, jwt, introspection, proxy, custom).REBAR_MCP_AUTH_ISSUER_URLenvOAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled.REBAR_MCP_AUTH_RESOURCE_SERVER_URLenvThe single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it.REBAR_MCP_AUTH_REQUIRED_SCOPESsecret required envComma-separated scopes a caller must hold; the SDK returns 403 insufficient_scope when a principal lacks one.REBAR_MCP_AUTH_STATIC_TOKENS_FILEenvPath to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens).REBAR_MCP_AUTH_JWT_JWKS_URIsecret required envHTTPS JWKS endpoint the `jwt` verifier fetches signing keys from (an OIDC provider's .well-known/jwks.json).REBAR_MCP_AUTH_JWT_ISSUERsecret required envExpected `iss` claim for the `jwt` verifier; falls back to REBAR_MCP_AUTH_ISSUER_URL when unset.REBAR_MCP_AUTH_JWT_ALGORITHMSsecret required envComma-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_LEEWAYsecret required envClock-skew leeway in seconds applied to exp/nbf validation by the `jwt` verifier (default 60).REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWNsecret required envMinimum seconds between JWKS refetches triggered by an unknown key id (the concurrency-safe flood guard; default 30).REBAR_MCP_AUTH_JWT_JWKS_TIMEOUTsecret required envHTTP timeout in seconds for the `jwt` verifier's JWKS fetch (default 10).REBAR_MCP_AUTH_JWT_EXPECTED_TYPsecret envWhen set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check.REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOSTenvSet to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ENDPOINTsecret required envThe `introspection` verifier's RFC 7662 endpoint URL (must be https://); the opaque token is POSTed here on every request (no caching).REBAR_MCP_AUTH_INTROSPECTION_CLIENT_IDsecret required envThe client id the `introspection` verifier presents to the Authorization Server via HTTP Basic (client_secret_basic).REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENVsecret required envThe NAME of the env var holding the introspection client secret (never the secret itself); must be present + non-empty at startup or the server refuses to start (fail-closed).REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOSTenvSet to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default.REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUDsecret required envSet to 1 to accept an active introspection response that OMITS `aud` (many AS do); off by default (fail-closed reject).REBAR_MCP_AUTH_PROXY_SECRET_ENVsecret required envThe NAME of the env var holding the trusted-proxy shared secret (never the secret itself); must be present + non-empty at startup or the `proxy` verifier refuses to start (fail-closed).REBAR_MCP_AUTH_PROXY_SECRET_HEADERsecret required envThe header the fronting proxy sends its shared secret on; the identity is trusted only when this matches (constant-time; default x-proxy-auth).REBAR_MCP_AUTH_PROXY_IDENTITY_HEADERsecret required envThe header carrying the proxy-authenticated principal identity, trusted only when the secret header validates (default x-forwarded-user).REBAR_MCP_AUTH_PROXY_SCOPESsecret required envComma-separated fixed scope set granted to proxy-authenticated principals; empty by default (the principal holds no scopes).REBAR_MCP_AUTH_CUSTOM_IMPORTsecret required envThe `custom` strategy's `module:factory` import string, resolving to a factory that returns a TokenVerifier; a TRUSTED operator config value that loads and executes the operator-configured code at st…
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account navapbc, which owns the repo
- ✓ Pass
Still maintained
Code last changed today
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for nava-rebar@0.16.0
Checks only this package version, not every dependency · checked Nov 15, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/navapbc-rebar)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 85% of the other 6182 servers in this category
- Published to the registry more recently than 87% of the other 6182 servers in this category
- Basic checks equal to or better than 99% of the other 6182 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Rebar safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: REBAR_MCP_AUTH_ENABLED, REBAR_MCP_AUTH_STRATEGIES, REBAR_MCP_AUTH_REQUIRED_SCOPES, 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_INTROSPECTION_ENDPOINT, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID, REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV, 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
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed today, and the latest version (0.16.0) reached the registry 5 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Rebar | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
- Three surfaces, one store — drive rebar as a CLI (
rebar), a Python library (import rebar), or an MCP server (rebar-mcp). - The tracker lives in the repo — tickets are an append-only event log on a
ticketsgit branch; no database, no daemon, and it travels with every clone. - Built for parallel agents — atomic claims, convergent merges, and provenance links let many agents and sessions write at once without lost work.
- Optional LLM gates — review a ticket's *plan* before work, its *completion* before close, and its *code* before it merges.
- Bidirectional Jira sync — a level-triggered reconciler keeps tickets and Jira in step, so teammates stay in the loop.
- Dogfooded through two independent gates — every change to rebar's own
mainmust pass an LLM code review and CI, on Gerrit, before it lands.
Install
pipx install nava-rebar # the `rebar` CLI (add [mcp] / [agents] for those extras)
brew install navapbc/rebar/rebar # or via Homebrew
Quickstart
Run one ticket end-to-end with the CLI or the Python library; the JSON block is the MCP server config so agents can drive the same loop over MCP. rebar --help (and rebar --help) is the authoritative command reference.
# CLI: one ticket through init -> create -> ready -> claim -> close
rebar init tid=$(rebar create task "Add a login page" -o json | python3 -c 'import json,sys; print(json.load(sys.stdin)["id"])') rebar ready # lists it as ready to work rebar claim "$tid" # open -> in_progress rebar transition "$tid" in_progress closed # in_progress -> closed
```python
import rebar # the same loop via the Python library tid = rebar.create_ticket("task", "Add a login page") rebar.claim(tid) rebar.transition(tid, "in_progress", "closed")
```json
{ "mcpServers": { "rebar": { "command": "uvx", "args": ["--from", "nava-rebar[mcp]", "rebar-mcp"] } } }
That's the whole loop — init → create → ready → claim → close. The CLI and Python blocks each drive one ticket end-to-end (the same id threaded through every step, no hard-coded id); the JSON is the MCP server config — add it to your client so an agent can run the same loop via the MCP tools. State is shared through the repo so many agents (and teammates via Jira) coordinate without stepping on each other.
How it works
rebar stores tickets as an append-only event log on a dedicated tickets git orphan branch (worktree at .tickets-tracker/); ticket state is computed by replaying events, and every write auto-commits and pushes so the store is shared immediately. A level-triggered reconciler bidirectionally syncs tickets with Jira. The branch name and worktree dir are configurable (tracker.branch / tracker.dir — see Configuration). Reads stay sub-second into the thousands of tickets; for measured numbers and git-growth expectations see docs/scale-envelope.md.
Documentation lives under docs/ — start with the docs index (grouped by audience: user / operator / contributor / agent) or the day-to-day user guide.
Why rebar
If you run coding agents against a repo, you eventually want to run *several* at once — and the moment you do, they need a shared place to coordinate. Most trackers weren't built for that:
- They're heavy. A daemon to babysit or a local database to keep running, with dependencies thick enough that a routine upgrade can break your work tracking across machines.
- They don't travel with the code. State lives outside the repo, so a fresh clone doesn't come with its tickets.
- They fight your git history. A tracker that writes to your working branch tangles ticket churn into your source-code commits.
- They have no concurrency story. Nothing stops two agents from claiming the same work or clobbering each other's state, and concurrent edits produce merge conflicts you resolve by hand — or lose.
- They buckle at scale. Speed and usability fall off past a few hundred tickets.
rebar's answer is to make the tracker part of the repo. Tickets are an append-only event log on a dedicated tickets orphan branch (linked in through a gitignored worktree); current state is a fast, deterministic replay of that log. That single decision pays off across the board:
- Zero infrastructure, fully portable. No database, no daemon — just git and a lightweight Python install. Clone the repo and the tracker comes with it.
- No commit interference. Ticket events live on their own branch and never touch your source history. Every write auto-commits and auto-pushes, so activity is shared in real time.
- Concurrency by design. Each event gets a globally-unique filename, so parallel writes merge as a clean union, and the rare conflicting fork resolves deterministically — every clone converges with no lost data.
claimis an atomic, optimistic-concurrency primitive: agents grab work without stepping on each other. - Built to scale. The event log plus cached replay stays fast as tickets grow.
On top of that foundation, rebar adds what parallel agent work actually needs:
- Bidirectional Jira sync — agents work in rebar, teammates work in Jira, and a level-triggered reconciler keeps the two in step. To run it automatically in CI, see docs/jira-sync-setup.md (the GitHub Actions reconcile-bridge + heartbeat-canary setup).
- Conflict-aware scheduling — tickets record their file impact, so
next-batchhands parallel agents work that won't collide on the same files. - Scratch space — an invisible per-ticket channel for subagents to pass notes to one another.
- Structural quality gates — clarity, acceptance-criteria, dispatch-readiness, and repo-wide health checks keep work dispatch-ready.
- LLM review gates *(optional).* Review an agent's plan before work starts, its completion before the ticket closes, and its code before it merges. Plan-review and code-review share one four-pass kernel. A finder cites evidence, a separate verifier tests each claim with atomic yes or no questions, and deterministic policy decides what blocks. A passing plan or completion review records an operation certificate as a DSSE envelope. The envelope carries an SSHSIG signature over its PAE bytes, produced with the signing environment's Ed25519 key. The certificate names that environment as its principal. The result is a machine-checkable process record for the reviewed work.
- Provenance links —
discovered_fromties emergent work back to the ticket that surfaced it. - One store, three interfaces — drive it from the CLI, a Python library, or the MCP server.
Requirements
System prerequisites:
- Python ≥ 3.11
gitis a runtime prerequisite because the store uses a Git orphan branch and worktree. The runtime engine uses in-process Python and does not requirebashorjq.- Git 2.38 or newer is required for development, tests, and CI. The floor is declared in
.github/git-version-floor.txt. The test suite and CI fail when Git is below that floor. - Deployments that use the optional S3 repair path require Git 2.38 or newer because that path invokes
git merge-tree --write-tree. - No external lock binary is required. Write serialization uses a two-window lock built entirely from the Python standard library — a
fcntl.flock(LOCK_EX)advisory lock plus an atomicmkdirlock (src/rebar/_store/lock.py) — so there is no dependency on util-linux's `flock` binary (or any other external tool). Themkdirwindow keeps mutual exclusion holding even wherefcntl.flockis unreliable (e.g. some network filesystems). acli(Atlassian CLI) — a required external binary for the Jira Cloud reconciliation/bridge path: everybridge/reconcileCloud mutation shells out to it, so it must be installed onPATH(install pointer: docs/jira-sync-setup.md). The[jira-datacenter]Data Center path does not need it — it uses thejiraPython library.
Python dependencies. A base install (pip install nava-rebar) provides the rebar CLI, the import rebar library, and the lean workflow engine. It installs pyyaml>=6 for the workflow DSL loader, jsonschema>=4.18 for schema registry and workflow input and output validation, and referencing>=0.30 for JSON Schema $ref resolution. The engine core and reconciler otherwise use the Python standard library. All other dependencies are optional extras that are imported lazily to keep the base installation light. CI verifies this boundary.
- Optional runtime capabilities — install what you serve:
- `[mcp]` installs the
rebar-mcpserver withmcp>=1.28.1,<2andpyjwt[crypto]>=2.10,<3. - `[agents]` — the LLM agent-operations framework + agentic workflow steps (
rebar review-plan, thecode_reviewworkflow): the provider-agnostic pydantic-ai runtime (pydantic-ai-slim[anthropic]) plusjson-repair. - Development & authoring extras — not needed to run or serve rebar:
- `[tracing]` — an OpenTelemetry OTLP trace sink (write-only; never read back into a rebar decision), for diagnostics.
- `[dev]` — the test/lint/type tooling (pytest, ruff, mypy, hatchling).
pip install -e '.[dev]'also self-references[agents]so the validation tests run rather than skip, and is required to run the full test suite (the interface-parity tests import the MCP server, so they error — not skip — withoutmcp).
See Install and Tests.
Install
rebar ships from one Python package — PyPI distribution `nava-rebar` (the import package and commands stay rebar / rebar-mcp). Pick the channel that fits. (System prerequisites in all cases: git (≥ 2.38 to develop/test rebar; see Requirements) and python3 (≥ 3.11); write serialization uses a built-in fcntl.flock + mkdir lock with no external binary; acli is required on PATH for the Jira Cloud reconciliation/bridge path (see docs/jira-sync-setup.md), while the [jira-datacenter] Data Center path does not need it.)
Homebrew (CLI)
brew install navapbc/rebar/rebar
or: brew tap navapbc/rebar && brew install rebar
Installs the rebar CLI (and the rebar library inside the formula's venv). For the MCP server via Homebrew users, install the [mcp] extra with pipx/uvx below.
PyPI — pipx / pip
**Runtime (prod) — install what you'l