outflow-mcp

outflow-mcp

An MCP (Model Context Protocol) server that exposes a live Outflow architecturegraph as context for AI coding agents — Claude Code, Claude Desktop, or anyother MCP-compatible client. Lets an agent ask "what does this file dependon", "what breaks if I change this", or "did my last batch of edits introducea circular dependency" against your workspace's real, currently-live graph.

It's a thin client over Outflow's existing /api/v1 REST API and theworkspace graph routes — no graph logicis duplicated here.

This package is developed inside the main Outflow monorepo but publishedfrom a standalone public mirror: https://github.com/laurells/outflow-mcp— that's the repo MCP registries/crawlers point at, and where npm publishruns from. Changes here get synced there before each release.

Setup

1. Create an API key for the workspace you want to expose. In Outflow,go to workspace settings → API Keys → create one. The raw key (ofk_...)is shown once — copy it.
2. Find your workspace ID — it's in the workspace URL(.../workspace/<id>/...) or workspace settings.
3. Build the server:

   cd packages/mcp-server
   npm install
   npm run build
   

4. Add it to your MCP client config. For Claude Code, add to your MCPsettings (claude mcp add or the equivalent config file):

   {
     "mcpServers": {
       "outflow": {
         "command": "node",
         "args": ["/absolute/path/to/outflow/packages/mcp-server/dist/index.js"],
         "env": {
           "OUTFLOW_BASE_URL": "https://your-outflow-domain.com",
           "OUTFLOW_API_KEY": "ofk_...",
           "OUTFLOW_WORKSPACE_ID": "your-workspace-id"
         }
       }
     }
   }
   

   For local development, OUTFLOW_BASE_URL defaults to http://localhost:3000if omitted.

Tools

All tools that take a path accept a partial match (e.g. "ApiClient" willmatch src/ApiClient.ts) — you never need to know Outflow's internalfile::/method:: ID format. An ambiguous partial match returns an errorlisting the candidates instead of guessing.

Notes

• This package is standalone — it is never bundled into server/ or web/,and has no build-time dependency on them. It only talks to a runningOutflow instance over HTTP using an API key, so it works equally wellpointed at localhost or a deployed instance.
• get_dependencies/get_impact and find_architecture_smells/find_pathcall workspace graph routes that (as of this package's introduction) wereextended to accept Authorization: Bearer ofk_... alongside the existingcookie-session auth — see server/src/graph/pathRouter.ts andsmellsRouter.ts.