Outflow Mcp

io.github.laurellsPublished by GitHub account laurellsv0.1.1Updated Oct 28, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Exposes a live Outflow workspace architecture graph to coding agents, so they can query dependencies, impact and health of tracked files.

What you can do
  • Look up nodes and list them by type, health or deprecation status
  • Inspect dependencies, blast radius and connection paths between files
  • Check overall architecture health and find smells such as circular dependencies, god nodes or dead code
  • Retrieve the whole graph at a chosen zoom level and recap the last coding session
  • Accept partial path matches, returning candidate lists instead of guessing
When to use it
Useful when an agent edits code in a project tracked by Outflow and needs to know what a file depends on, what breaks if it changes, or whether recent edits introduced circular dependencies.
Requirements
Runs locally as an npm package over stdio. Needs a running Outflow instance (OUTFLOW_BASE_URL, defaulting to an API key in OUTFLOW_API_KEY, and the target workspace ID in OUTFLOW_WORKSPACE_ID. Desktop MCP client only.
Before you install
Requires a workspace API key that is shown only once at creation; store it in the client config rather than sharing it. The server reads architecture data from your Outflow instance over HTTP, so point it only at instances you trust. Tools are read-only queries per the README.

Installation

In SourceWeft

  1. Open Outflow Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:
    bash
    cd packages/mcp-servernpm installnpm 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):
    json
    {  "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.

Source: README.md at commit af7fb2d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.