openfabriq
MCP server

Overview

Ask Claude about your factory, in your own conversations. Nine tools that read it and change nothing.

Ask Claude why a run failed, what the factory cost this week, or what waits for you. openfabriq gives Claude Code, Claude Desktop and claude.ai nine tools that read your factory and change nothing.

This page is about Claude reading your factory. To give your agents tools from other services, such as Sentry, see MCP servers.

What you can ask

Ask, for exampleWhat Claude readsTool
What does the factory do? Which agent can merge?The factory: agents, automations, what they may do, limitsfactory_overview
Which runs failed today?The runs, latest firstlist_runs
Why did the last run fail?One run: its prompt, what the agent did, its outputsread_run
When does the nightly audit run next?The scheduled automationsschedules
What does the wiki say about the deploy?The project's wikiread_wiki
Why does Slack not answer?Each integration: connected or not, and how to connect itconnections
Is this change to openfabriq/ valid?What validate and plan would say, without writing anythingcheck_factory_change
How much did the factory cost this week, per agent?Runs, cost, pull requests, human interventionsmetrics
Which issues are waiting for me?Where each issue or pull request standsboard

Their parameters are in Tools.

Connect Claude

Pick where your engine runs.

Claude Code: with the openfabriq plugin, there is nothing to do. Without it:

claude mcp add --scope user openfabriq -- openfabriq mcp

Claude Desktop: Settings › Developer › Edit Config, add these lines, then restart Claude Desktop:

claude_desktop_config.json
{
  "mcpServers": {
    "openfabriq": {
      "command": "openfabriq",
      "args": ["mcp"]
    }
  }
}

If it says the server failed to start, put the full path that which openfabriq prints in command.

Good to know

  • Read only. No run started, nothing written to GitHub or to the factory. To change the factory, ask Claude for the change, merge it in a pull request, and run openfabriq apply. To start a run: openfabriq run.
  • Several projects. Claude reads every project of the engine. With more than one, it names the one it asks about (owner/repo).
  • Always current. Each question reads the factory as last applied, even when the engine is stopped.
  • Signing out, on a server. Claude stays connected for 30 days after its last question. To sign everyone out, change the studio's password (with GitHub, generate a new client secret), or delete ~/.openfabriq/mcp-grants.json on the engine. With GitHub, someone removed from the repositories loses access within the hour.

Security

  • What the tools ask GitHub, Linear or Sentry is read-only too. connections says whether a service is connected, never its token.
  • Issues, pull requests and transcripts are written by others: openfabriq tells Claude they are data, never instructions.
  • Claude sees what the tools return, transcripts included: use it with code you would show it anyway.
  • On a server, only Claude and Claude Code can sign in, allowed by someone signed in with GitHub, or else with the studio's password. After 10 wrong passwords in 10 minutes from one address, that address waits 10 minutes.

On this page