MCP Tools DirectoryAbout this integration
MCP server exposing an Outflow workspace's live architecture graph as context for AI coding agents
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- outflow-mcp
- Last compatibility test
- Not independently tested
Connect your agent
outflow-mcpPublisher README and package manifest reviewed from pinned captures. The package and Outflow endpoint were not executed. Access is bounded by the supplied workspace-scoped API credentials.
Capabilities: Find architecture nodes, List dependencies and impact, Find graph paths and architecture smells, Report architecture health, Summarize the last coding session
Connected profiles
Additional details
io.github.laurells/outflow-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17OUTFLOW_API_KEY, OUTFLOW_WORKSPACE_ID
Source ↗ · Checked 2026-09-17outflow-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19An MCP client launches the Node entrypoint as a configured subprocess; the standalone server then queries a running Outflow instance rather than embedding graph logic.
Source ↗ · Checked 2026-09-19Requires an Outflow API key and workspace ID. The base URL selects the Outflow instance and otherwise defaults to localhost for local development.
Source ↗ · Checked 2026-09-19Configure the MCP client with node and the built dist/index.js path, passing OUTFLOW_BASE_URL, OUTFLOW_API_KEY, and OUTFLOW_WORKSPACE_ID as environment variables.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19