rebar MCP Server

What this does

rebar exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

REBAR_ROOT
REBAR_MCP_READONLY
REBAR_MCP_ALLOW_LLM
REBAR_MCP_DEDUP
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

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install rebar?

Run the Claude Code command in the install section to add rebar to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with rebar?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to rebar as well.

Does rebar need an API key?

This listing does not flag an API key as required. The server can use these environment variables: REBAR_ROOT, REBAR_MCP_READONLY, REBAR_MCP_ALLOW_LLM, REBAR_MCP_DEDUP, 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; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.