A connection that lets an agent ask questions about repositories managed by Rebar, a tool for coordinating coding-agent work. It starts a local server that provides access to repositories under a configured directory.

Use it when an agent needs to connect to Rebar's repository-question service. The available information only supports describing it as a repository access and question interface.

It gives the agent a defined way to obtain repository information through Rebar instead of relying only on the current conversation. The description does not specify which questions or repository operations are supported.

rebar-ask — MCP server for Claude Code and Codex by willackerly: A connection that lets an agent ask questions about…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/willackerly/rebar/rebar-ask

Clone the repo

git clone --depth 1 https://github.com/willackerly/rebar

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

rebar-ask scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 10 lines

What it actually says

{
  "rebar-ask": {
    "command": "/Users/will/dev/rebar/bin/ask-mcp-server",
    "args": [
      "--stdio",
      "--repos-dir",
      "/Users/will/dev"
    ]
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 10 lines scan A 12895840bf5c

Subscribe to this mod's changes

rebar-ask is an MCP server published in the GitHub repository willackerly/rebar (5 stars, last pushed 21d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents ai-agents claude contract-driven-development developer-methodology multi-agent-systems

rebar-ask

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

zymi-release

grep_app

linkedin-writer

hivemind

conversation-agents

docs-langchain