MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents
Connect Runs on your machine
claude mcp add outflow-mcp -e OUTFLOW_BASE_URL=<OUTFLOW_BASE_URL> -e OUTFLOW_API_KEY=<OUTFLOW_API_KEY> -e OUTFLOW_WORKSPACE_ID=<OUTFLOW_WORKSPACE_ID> -- npx -y [email protected]{
"mcpServers": {
"outflow-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"OUTFLOW_BASE_URL": "<OUTFLOW_BASE_URL>",
"OUTFLOW_API_KEY": "<OUTFLOW_API_KEY>",
"OUTFLOW_WORKSPACE_ID": "<OUTFLOW_WORKSPACE_ID>"
}
}
}
}{
"mcpServers": {
"outflow-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"OUTFLOW_BASE_URL": "<OUTFLOW_BASE_URL>",
"OUTFLOW_API_KEY": "<OUTFLOW_API_KEY>",
"OUTFLOW_WORKSPACE_ID": "<OUTFLOW_WORKSPACE_ID>"
}
}
}
}{
"servers": {
"outflow-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"OUTFLOW_BASE_URL": "<OUTFLOW_BASE_URL>",
"OUTFLOW_API_KEY": "<OUTFLOW_API_KEY>",
"OUTFLOW_WORKSPACE_ID": "<OUTFLOW_WORKSPACE_ID>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
OUTFLOW_BASE_URLOptional | Base URL of your running Outflow instance. Defaults to http://localhost:3000 if omitted. |
OUTFLOW_API_KEYRequired, 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_IDRequired | ID of the workspace to expose. Found in the workspace URL (.../workspace/<id>/...) or workspace settings. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 17 Jul 2026 |
| Last updated | 17 Jul 2026 |
| Registry name | io.github.laurells/outflow-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.