rebar MCP Setup & Guide
io.github.navapbc/rebar · v0.13.1
Event-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server.
Copy the install config on this page first, then verify docs and permissions upstream.
Overview
Event-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server. rebar is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.
Use cases
AgentHub Verified AvailabilityTested & Ready
Automated pipeline validated install commands, protocol & client compatibility
Copy by platform
Choose your platform
- Open or create .cursor/mcp.json in your project root
- Click Copy config and paste; merge only this mcpServers entry if others exist
- Replace <placeholders> in env with real secrets (see Environment variables below)
- Save, then Cmd+Shift+P → Reload Window
Pre-fill Environment Variables (Optional)
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Setup tutorial
- Open the rebar page and confirm this MCP Server (source: MCP Registry).
- Copy the Cursor, Claude Code, or VS Code snippet.
- Merge it into mcpServers and replace env placeholders with real secrets.
- Reload the window, then call the MCP tools from your agent chat.
Install commands
Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.
Claude Code (local)
- Install Claude Code CLI
- Copy the command below, replace <placeholders> with real env values, then run in terminal
- See Environment variables below if listed
claude mcp add rebar -- uvx nava-rebarCursor — .cursor/mcp.json (local)
- Open or create .cursor/mcp.json in your project root
- Click Copy config and paste; merge only this mcpServers entry if others exist
- Replace <placeholders> in env with real secrets (see Environment variables below)
- Save, then Cmd+Shift+P → Reload Window
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}VS Code — .vscode/mcp.json (local)
- Install GitHub Copilot in VS Code with MCP support
- Open or create .vscode/mcp.json in your project root
- Click Copy config and paste; merge only this mcpServers entry if others exist
- Replace <placeholders> in env with real secrets
- Save and Developer: Reload Window
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Claude Desktop — claude_desktop_config.json (local)
- Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
- Click Copy config and merge under mcpServers
- Replace <placeholders> in env with real secrets
- Fully quit and restart Claude Desktop
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Trae — .trae/mcp.json (local)
- Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
- Click Copy config and merge mcpServers
- Replace <placeholders> in env with real secrets
- Save and reload Trae
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Cherry Studio — MCP settings (local)
- Cherry Studio → Settings → MCP Servers → Add (STDIO)
- Or import JSON: click Copy config and merge mcpServers
- Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
- Enable the server and check tools load
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Tongyi Lingma — MCP config (local)
- Lingma Settings → MCP → + → STDIO or config file
- Click Copy config and merge mcpServers
- Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
- Confirm connected before using tools in agent chat
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Windsurf — mcp_config.json (local)
- Edit ~/.codeium/windsurf/mcp_config.json
- Click Copy config and merge mcpServers (stdio same as Cursor)
- Replace <placeholders> in env, save, refresh Cascade
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Cline — MCP Servers (local)
- Cline panel → Settings → MCP Servers
- Click Copy config and merge
- Replace <placeholders> in env, then save
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}WorkBuddy — .workbuddy/mcp.json (local)
- Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
- Or Plugins → MCP Servers → Configure MCP and paste the JSON below
- Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
- Save, restart WorkBuddy, confirm connector status is green
{
"mcpServers": {
"rebar": {
"command": "uvx",
"args": [
"nava-rebar"
]
}
}
}Troubleshooting & Common ErrorsFAQ
Common connection errors and verified fixes for rebar
Getting 'connection closed' or exit code 1 in Cursor / Claude Code for rebar?
Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.
# Check binary path in terminal: which npx node -v
Getting 'spawn npx ENOENT' or 'command not found'?
The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).
Missing required environment variable or authentication failure?
rebar requires environment variables (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). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.
// .cursor/mcp.json 或 claude_desktop_config.json
{
"env": {
"API_KEY": "your_actual_key_here"
}
}Tool Mock Playground
Sandboxrebar Tool Interface Simulation · Preview tool schema & outputs without local runtime
{
"target": "rebar",
"action": "execute",
"options": {
"mode": "standard",
"timeoutMs": 5000
}
}Click 'Run Mock' above
to preview the raw response returned to the LLM
Decision Guide: Why & When to Use
Assess suitability before installing to save trial-and-error time
- PR review
- Changelog generation
- Cross-repo issue search
- Replacing human security audit
- Unauthorized repo access
rebar + Scenario Prompt → Complete Agent Automation
MCP hands-on: install to visible results
Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.
Related resources
顺序思考
io.mcp-cn.modelcontextprotocol/server-sequential-thinking
帮助AI进行结构化思考和推理的MCP工具
n8n
io.mcp-cn.drballs/n8n-mcp-server
n8n工作流自动化平台的MCP服务器,提供完整的工作流管理、执行控制、凭证管理等功能
Playwright
io.mcp-cn.playwright/mcp
基于Playwright的自动化测试和网页操作MCP工具
GitHub
io.mcp-cn.modelcontextprotocol/server-github
连接GitHub的MCP服务器,支持仓库管理、问题跟踪、代码搜索等功能
高德地图
io.mcp-cn.amap/amap-maps-mcp-server
高德地图的MCP服务器
Figma
io.mcp-cn.figma-developer-mcp
连接Figma的MCP服务器,支持设计文件管理和操作
Often paired with
API Gateway
v1.2.25
io.clawhub.byungkyu/api-gateway
Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, etc.
v1.2.6
io.clawhub.byungkyu/linkedin-api
LinkedIn API integration with managed OAuth. Share posts, manage profile, and access LinkedIn features. Use this skill when users want to share content on LinkedIn, get profile/organization information, or interact with LinkedIn's platform.
WhatsApp Business
v1.2.8
io.clawhub.byungkyu/whatsapp-business
WhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact with WhatsApp Business. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Salesforce
v1.2.7
io.clawhub.byungkyu/salesforce-api
Salesforce CRM API integration with managed OAuth. Install only if you need Salesforce CRM administration. Connect with the narrowest Salesforce permissions available, prefer sandbox orgs for destructive or batch work, verify the intended connection ID before each request, etc.
Keep exploring AgentHub
Most people compare similar tools or check scenario guides before installing—start here.
Listing badge: put AgentHub on your site
Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.
<a href="https://myagenthub.cn/p/io.github.navapbc/rebar" title="Listed on AgentHub: rebar" target="_blank" rel="noopener">
<img src="https://myagenthub.cn/badge/io.github.navapbc/rebar?lang=en" alt="Listed on AgentHub: rebar" height="20" style="border:0"/>
</a>[](https://myagenthub.cn/p/io.github.navapbc/rebar)Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.
Unified Manifest
{
"id": "io.github.navapbc/rebar",
"type": "mcp-server",
"version": "0.13.1",
"displayName": "rebar",
"description": "Event-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server.",
"repository": {
"url": "https://github.com/navapbc/rebar",
"source": "github"
},
"distribution": {
"packages": [
{
"registryType": "pypi",
"identifier": "nava-rebar",
"version": "0.13.1",
"runtimeHint": "uvx",
"transport": "stdio",
"environmentVariables": [
{
"name": "REBAR_ROOT",
"description": "Path to the repo root that holds the .tickets-tracker store (defaults to the git toplevel of the working dir)."
},
{
"name": "REBAR_MCP_READONLY",
"description": "Set to 1 to expose only the read tools (no write/mutation tools)."
},
{
"name": "REBAR_MCP_ALLOW_LLM",
"description": "Set to 1 to enable the billable LLM tools (review_code / scan_spec / verify_completion / review_plan); off by default."
},
{
"name": "REBAR_MCP_ALLOW_JIRA_SYNC",
"description": "Set to 1 to allow the live (mutating) Jira reconcile mode; otherwise reconcile is dry-run only."
},
{
"name": "REBAR_MCP_TRANSPORT",
"description": "Transport for the MCP server: 'stdio' (default) or 'http' (the optional Streamable-HTTP transport)."
},
{
"name": "REBAR_MCP_HTTP_HOST",
"description": "Bind host for the Streamable-HTTP transport (default 127.0.0.1)."
},
{
"name": "REBAR_MCP_HTTP_PORT",
"description": "Bind port for the Streamable-HTTP transport (1-65535; default 8000)."
},
{
"name": "REBAR_MCP_HTTP_PATH",
"description": "URL path the Streamable-HTTP transport serves on (default /mcp)."
},
{
"name": "REBAR_MCP_HTTP_ALLOWED_HOSTS",
"description": "Comma-separated allowlist of exact host:port values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback."
},
{
"name": "REBAR_MCP_HTTP_ALLOWED_ORIGINS",
"description": "Comma-separated allowlist of exact Origin values accepted by the Streamable-HTTP DNS-rebinding protection; empty defaults to loopback."
},
{
"name": "REBAR_MCP_HTTP_TLS_AT_EDGE",
"description": "Set to 1 to acknowledge TLS is terminated at the edge; required to bind the Streamable-HTTP transport to a non-loopback host."
},
{
"name": "REBAR_MCP_ALLOW_UNAUTHENTICATED_HTTP",
"description": "Set to 1 to acknowledge running the Streamable-HTTP transport without a token verifier; required to boot the HTTP transport while auth is off."
},
{
"name": "REBAR_MCP_AUTH_ENABLED",
"description": "Set to 1 to enable MCP authentication (the composite token verifier + Resource-Server wiring); off by default."
},
{
"name": "REBAR_MCP_AUTH_STRATEGIES",
"description": "Comma-separated, ordered list of token-verifier strategies to compose (closed set: static, jwt, introspection, proxy, custom)."
},
{
"name": "REBAR_MCP_AUTH_ISSUER_URL",
"description": "OAuth authorization-server issuer URL advertised in the Protected-Resource Metadata (RFC 9728) when auth is enabled."
},
{
"name": "REBAR_MCP_AUTH_RESOURCE_SERVER_URL",
"description": "The single resource identifier (RFC 8707 audience) for this server; the composite verifier re-checks every accepted token against it."
},
{
"name": "REBAR_MCP_AUTH_REQUIRED_SCOPES",
"description": "Comma-separated scopes a caller must hold; the SDK returns 403 insufficient_scope when a principal lacks one."
},
{
"name": "REBAR_MCP_AUTH_STATIC_TOKENS_FILE",
"description": "Path to the JSON secrets file for the static-bearer verifier (stores only SHA-256 digests of the accepted tokens)."
},
{
"name": "REBAR_MCP_AUTH_JWT_JWKS_URI",
"description": "HTTPS JWKS endpoint the `jwt` verifier fetches signing keys from (an OIDC provider's .well-known/jwks.json)."
},
{
"name": "REBAR_MCP_AUTH_JWT_ISSUER",
"description": "Expected `iss` claim for the `jwt` verifier; falls back to REBAR_MCP_AUTH_ISSUER_URL when unset."
},
{
"name": "REBAR_MCP_AUTH_JWT_ALGORITHMS",
"description": "Comma-separated PINNED, asymmetric-only JWS algorithms for the `jwt` verifier (default RS256,ES256); a symmetric algorithm on a JWKS source is refused."
},
{
"name": "REBAR_MCP_AUTH_JWT_LEEWAY",
"description": "Clock-skew leeway in seconds applied to exp/nbf validation by the `jwt` verifier (default 60)."
},
{
"name": "REBAR_MCP_AUTH_JWT_JWKS_REFETCH_COOLDOWN",
"description": "Minimum seconds between JWKS refetches triggered by an unknown key id (the concurrency-safe flood guard; default 30)."
},
{
"name": "REBAR_MCP_AUTH_JWT_JWKS_TIMEOUT",
"description": "HTTP timeout in seconds for the `jwt` verifier's JWKS fetch (default 10)."
},
{
"name": "REBAR_MCP_AUTH_JWT_EXPECTED_TYP",
"description": "When set, the `jwt` verifier requires the JWT header `typ` to equal this (e.g. at+JWT per RFC 9068); unset skips the check."
},
{
"name": "REBAR_MCP_AUTH_JWT_ALLOW_PRIVATE_JWKS_HOST",
"description": "Set to 1 to permit a private/link-local/loopback JWKS host (SSRF guard is on by default); off by default."
},
{
"name": "REBAR_MCP_AUTH_INTROSPECTION_ENDPOINT",
"description": "The `introspection` verifier's RFC 7662 endpoint URL (must be https://); the opaque token is POSTed here on every request (no caching)."
},
{
"name": "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_ID",
"description": "The client id the `introspection` verifier presents to the Authorization Server via HTTP Basic (client_secret_basic)."
},
{
"name": "REBAR_MCP_AUTH_INTROSPECTION_CLIENT_SECRET_ENV",
"description": "The 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)."
},
{
"name": "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_PRIVATE_HOST",
"description": "Set to 1 to permit a private/link-local/loopback introspection endpoint host (SSRF guard is on by default); off by default."
},
{
"name": "REBAR_MCP_AUTH_INTROSPECTION_ALLOW_MISSING_AUD",
"description": "Set to 1 to accept an active introspection response that OMITS `aud` (many AS do); off by default (fail-closed reject)."
},
{
"name": "REBAR_MCP_AUTH_PROXY_SECRET_ENV",
"description": "The 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)."
},
{
"name": "REBAR_MCP_AUTH_PROXY_SECRET_HEADER",
"description": "The header the fronting proxy sends its shared secret on; the identity is trusted only when this matches (constant-time; default x-proxy-auth)."
},
{
"name": "REBAR_MCP_AUTH_PROXY_IDENTITY_HEADER",
"description": "The header carrying the proxy-authenticated principal identity, trusted only when the secret header validates (default x-forwarded-user)."
},
{
"name": "REBAR_MCP_AUTH_PROXY_SCOPES",
"description": "Comma-separated fixed scope set granted to proxy-authenticated principals; empty by default (the principal holds no scopes)."
},
{
"name": "REBAR_MCP_AUTH_CUSTOM_IMPORT",
"description": "The `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 startup (fail-closed on any load error)."
}
]
}
],
"remotes": []
},
"dependencies": [],
"installTargets": [
"claude-code",
"claude-desktop",
"cursor",
"vscode",
"trae",
"cherry-studio",
"lingma",
"windsurf",
"cline",
"workbuddy"
],
"keywords": [],
"provenance": {
"origin": "official-mcp-registry",
"originalId": "io.github.navapbc/rebar",
"originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.navapbc%2Frebar/versions/latest",
"isOfficial": true,
"status": "active"
}
}