English Français العربية

io.github.laurells/outflow-mcp

Registre officiel Outils de développement

MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package outflow-mcp
Claude Code 
claude mcp add outflow-mcp -e 'OUTFLOW_BASE_URL=<OUTFLOW_BASE_URL>' -e 'OUTFLOW_API_KEY=<your outflow_api_key>' -e 'OUTFLOW_WORKSPACE_ID=<OUTFLOW_WORKSPACE_ID>' -- npx -y outflow-mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "outflow-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "outflow-mcp@0.1.1"
            ],
            "env": {
                "OUTFLOW_BASE_URL": "<OUTFLOW_BASE_URL>",
                "OUTFLOW_API_KEY": "<your outflow_api_key>",
                "OUTFLOW_WORKSPACE_ID": "<OUTFLOW_WORKSPACE_ID>"
            }
        }
    }
}

Variables d'environnement

  • OUTFLOW_BASE_URL Base URL of your running Outflow instance. Defaults to http://localhost:3000 if omitted.
  • OUTFLOW_API_KEY obligatoire secret API key for the workspace to expose. Create one from workspace settings in Outflow (Settings → API Keys) — the raw key (ofk_...) is shown once.
  • OUTFLOW_WORKSPACE_ID obligatoire ID of the workspace to expose. Found in the workspace URL (.../workspace/<id>/...) or workspace settings.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. outflow-mcp
  2. Setup
  3. Tools
  4. Notes

outflow-mcp

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

It's a thin client over Outflow's existing /api/v1 REST API and the workspace graph routes — no graph logic is duplicated here.

This package is developed inside the main Outflow monorepo but published from a standalone public mirror: **https://github.com/laurells/outflow-mcp** — that's the repo MCP registries/crawlers point at, and where npm publish runs 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 MCP settings (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:3000 if omitted.

Tools

ToolUse it to ask
find_nodeIs this file tracked? What's its ID?
list_nodesWhat's deprecated / low health / a given type?
get_dependenciesWhat does this file rely on?
get_impactWhat breaks if I change this file? (blast radius)
find_pathHow are these two files connected?
get_architecture_healthWhat's the overall health grade and at-risk nodes?
find_architecture_smellsAny circular deps, god nodes, or dead code right now?
get_architecture_graphGive me the whole graph at a zoom level.
get_last_session_recapWhat happened in my last coding session?

All tools that take a path accept a partial match (e.g. "ApiClient" will match src/ApiClient.ts) — you never need to know Outflow's internal file::/method:: ID format. An ambiguous partial match returns an error listing 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 running Outflow instance over HTTP using an API key, so it works equally well pointed at localhost or a deployed instance.
  • get_dependencies/get_impact and find_architecture_smells/find_path call workspace graph routes that (as of this package's introduction) were extended to accept Authorization: Bearer ofk_... alongside the existing cookie-session auth — see server/src/graph/pathRouter.ts and smellsRouter.ts.

Questions fréquentes

Qu'est-ce que io.github.laurells/outflow-mcp ?

MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents

Comment installer io.github.laurells/outflow-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add outflow-mcp -e 'OUTFLOW_BASE_URL=<OUTFLOW_BASE_URL>' -e 'OUTFLOW_API_KEY=<your outflow_api_key>' -e 'OUTFLOW_WORKSPACE_ID=<OUTFLOW_WORKSPACE_ID>' -- npx -y outflow-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.laurells/outflow-mcp ?

Oui. Il attend OUTFLOW_API_KEY, OUTFLOW_WORKSPACE_ID, à renseigner dans sa configuration.

io.github.laurells/outflow-mcp est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.laurells/outflow-mcp ?

Il est publié par laurells. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.