agentflow-mcp
This server is an enterprise architecture knowledge MCP server that provides structured data to agents for architecture, platform selection, risk governance, and branding.
Look up reference architecture patterns (
arch_pattern_lookup) by industry, data stack, cloud, and constraints, returning components, data zones, integration notes, confidence scores, and diagram data.Recommend data platforms (
tool_selection_lookup) based on use case, data stack, constraints, and latency, with cloud fit, reasoning, and alternatives.Get risk and governance policies (
risk_policy_lookup) including required controls, risk flags, and human-in-the-loop triggers for regulated data.Retrieve company brand context (
brand_context_lookup) for a domain, including name, description, tags, positioning, brand voice/style, and logo URL, with caching and graceful fallback.Run locally or over HTTP (stdio or streamable HTTP) for integration with MCP clients and scale-to-zero deployment on Fly.io.
Use offline source data for the first three tools, with optional Brandfetch and logo.dev API keys for brand lookups.
Provides Databricks-specific architecture and platform guidance, including recommending Databricks as a data platform, assessing cloud fit, and surfacing alternative platforms with rationale based on workload, constraints, and latency.
Provides Snowflake-specific architecture and platform guidance, including recommending Snowflake as a data platform, assessing cloud fit, and surfacing alternative platforms with rationale based on workload, constraints, and latency.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agentflow-mcp What architecture pattern fits a media agency using BigQuery with EU data residency?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agentflow-mcp
An enterprise architecture knowledge MCP server for the agentflow demo pipeline. Built with the MCP TypeScript SDK v2 + TypeScript, deployed on Fly.io.
The server exposes four tools that ground an Architecture Agent and Risk Checker Agent in curated enterprise patterns rather than generic LLM reasoning:
Tool | Called by | Returns |
| Architect Agent | Reference architecture pattern, components, diagram data |
| Architect Agent | Platform recommendation with constraint-aware reasoning |
| Risk Checker Agent | Required controls, risk flags, HITL trigger |
| Architect Agent | Company identity, positioning, logo (via Brandfetch + logo.dev) |
How It Fits In
agentflow pipeline agentflow-mcp
┌──────────────────────┐ ┌───────────────────────┐
│ Qualifier Agent │ │ arch_pattern_lookup │
│ - clarifies the ask │ │ tool_selection_lookup │
└──────┬───────────────┘ │ risk_policy_lookup │
│ handoff │ brand_context_lookup │
┌──────▼───────────────┐ │ │
│ Architect Agent │──── MCP calls ───▶│ Source pack (data/) │
│ - pattern selection │ │ 102 markdown files │
│ - tool selection │◀── JSON response ─│ with YAML frontmatter │
│ - diagram rendering │ │ │
└──────┬───────────────┘ │ Brandfetch + logo.dev │
│ handoff │ (cached, additive) │
┌──────▼───────────────┐ └───────────────────────┘
│ Risk Checker Agent │──── risk_policy_lookup ──▶
│ - HITL gate trigger │◀── risk_flags, HITL ──
└──────────────────────┘The MCP is a tool provider, not an agent orchestrator. Agent prompts and the architecture-diagram skill live in the agentflow project. The MCP provides structured data; the agents interpret and act on it.
Related MCP server: MCP Architect
Quickstart
Prerequisites
Node.js >= 20
(Optional) Brandfetch API key and logo.dev key for
brand_context_lookup
Install & Run
npm install
npm run dev # stdio transport (local dev + MCP Inspector)HTTP transport (streamable HTTP)
MCP_TRANSPORT=http-stream PORT=8080 npm run dev
# agentflow-mcp listening on http://0.0.0.0:8080/mcpThe http-stream transport runs in stateless mode (hardcoded in src/index.ts). This is required for compatibility with standard MCP clients: their startup "probe" is a GET with no session ID, which a stateful server answers with 400 No sessionId (surfaced by clients as a fatal "version negotiation failed" error). Stateless mode answers that probe with 405 Method Not Allowed + Allow: POST, which every client explicitly tolerates. It also suits scale-to-zero deployments (Fly.io) — no server-side session state to lose when instances spin down.
Run Tests
npm test # 31 unit + integration tests
npm run typecheck # tsc --noEmit
npm run check # biome lint + formatEnvironment Variables
Copy .env.example to .env and fill in the keys. Only brand_context_lookup needs external API keys — the other three tools work offline from the source pack.
Variable | Required by | Purpose |
|
| Bearer token for Brandfetch Brand Context API |
|
| Bearer token for logo.dev Brand API |
|
| Publishable key for logo.dev CDN URLs |
| Server |
|
| Server | HTTP port (default 8080, used when transport is |
| Server | Graylog GELF HTTP input URL (e.g. |
| Server | Source name for Graylog messages (default |
When API keys are missing, brand_context_lookup returns cached responses for cached domains or a graceful unavailable response for uncached domains. The other three tools continue to function normally.
Tools
arch_pattern_lookup
Match an enterprise ask to a curated reference architecture pattern.
Input:
{
"industry": "media_agency",
"data_stack": ["BigQuery", "Snowflake"],
"cloud": "GCP",
"constraints": ["SAML SSO", "EU data residency", "cross-client governance"],
"latency": "batch"
}Output:
{
"pattern_id": "media_agency_audience_measurement",
"architecture_summary": "...",
"recommended_components": ["BigQuery", "Snowflake", "SAML SSO", "GCP EU Region"],
"data_zones": ["bronze", "silver", "gold"],
"integration_notes": ["..."],
"confidence": 0.87,
"diagram_data": {
"components": [{ "name": "BigQuery", "type": "database", "sublabel": "...", "zone": "gold" }],
"connections": [{ "from": "Users", "to": "SAML SSO", "label": "OAuth 2.0", "style": "dashed" }],
"boundaries": [{ "label": "GCP EU Region", "type": "region" }]
},
"source_references": [{ "path": "data/patterns/...", "title": "...", "source_url": "..." }]
}Matching logic: Deterministic, rules-based — industry match (40%) → data stack overlap (30%) → constraint coverage (30%). Curated matches (confidence >= 0.85) include diagram_data and source references. Weak matches fall back to a generic enterprise AI POC pattern with confidence < 0.5.
tool_selection_lookup
Recommend a platform based on workload, data stack, constraints, and latency.
Input:
{
"use_case": "AI-powered patient insights",
"data_stack": ["Databricks"],
"constraints": ["HIPAA", "PHI", "US data residency"],
"latency": "batch"
}Output:
{
"recommended_platform": "Databricks",
"cloud_fit": "Azure or AWS",
"reasoning": "Strong lakehouse fit for healthcare AI with HIPAA-compliant governance...",
"alternatives": [{ "platform": "Snowflake", "rationale": "..." }, { "platform": "BigQuery", "rationale": "..." }]
}risk_policy_lookup
Return industry-specific risk and governance checks, including HITL triggers for regulated data.
Input:
{
"industry": "healthcare",
"data_classification": ["PHI", "PII"],
"region": "US",
"deployment": "cloud",
"constraints": ["HIPAA"]
}Output:
{
"required_controls": ["RBAC", "audit logs", "data lineage", "SAML SSO"],
"risk_flags": ["prompt leakage", "overbroad analyst access"],
"hitl_required": true,
"review_reason": "PHI access requires human approval before final architecture signoff"
}HITL is triggered for regulated data types (PHI, PII, regulated financial data) with a human-readable review_reason.
brand_context_lookup
Retrieve rich company context from Brandfetch and a logo from logo.dev, with layered caching.
Input:
{
"domain": "havas.com"
}Output:
{
"company_name": "Havas",
"domain": "havas.com",
"industry_hint": "media_agency",
"description": "...",
"tags": ["advertising", "marketing", "media"],
"positioning": { "value_proposition": "...", "target_audience": "...", "products_and_services": "..." },
"brand": { "voice": "...", "style": "..." },
"logo_url": "https://...",
"confidence": 0.85
}Caching layers: (1) Brandfetch cachedOnly=true for instant cache-only lookups, (2) local file cache with TTL. Repeated lookups return cached data without consuming API quota. Graceful fallback when APIs are unreachable.
Source Pack
The data/ directory contains 102 markdown files with structured YAML frontmatter, organized into:
data/
├── industry/ # Industry-specific architecture notes
├── vendors/ # Vendor documentation (GCP, AWS, Azure, Snowflake, Databricks)
└── patterns/ # Curated reference architecture patterns (4 demo scenarios)Frontmatter fields: type, title, source_url, vendor, industry, data_stack, cloud, constraints, compliance, region, data_zones, latency, pattern_id, architecture_summary, recommended_components, integration_notes, confidence_baseline, diagram_data.
The source pack is loaded into an in-memory index at server startup, keyed by industry, data stack, constraints, and pattern_id.
Demo Scenarios
Scenario | Industry | Pattern ID |
Media agency audience measurement |
|
|
Healthcare patient insights |
|
|
Retail lakehouse personalization |
|
|
FSI governance copilot |
|
|
Deployment
Docker
docker build -t agentflow-mcp .
docker run -p 8080:8080 agentflow-mcpFly.io
Simplest deployment path — no IAM setup, deploys your Dockerfile directly:
# Install Fly CLI (if not already)
curl -L https://fly.io/install.sh | sh
# Create the app (one-time)
fly launch --no-deploy
# Set secrets
fly secrets set BRANDFETCH_API_KEY=your-key-here
fly secrets set LOGO_DEV_SECRET_KEY=your-key-here
fly secrets set LOGO_DEV_PUBLISHABLE_KEY=your-key-here
# Deploy
fly deployfly.toml is already configured: Node 22 Docker image, HTTP transport on port 8080, scale-to-zero when idle. The MCP endpoint will be at https://agentflow-mcp.fly.dev/mcp (or a custom domain such as https://arch.ishlab.dev/mcp).
Note: the server runs http-stream in stateless mode — do not switch it back to stateful, or standard MCP clients will fail their startup probe with "version negotiation failed" (see HTTP transport).
Scripts
Script | Purpose |
| Validate all markdown files in |
| Generate frontmatter for source pack files |
| Verify all four tools are discoverable via MCP tool listing |
| Pre-populate the brand cache for the four demo domains |
npx tsx scripts/validate-source-pack.ts # validate source pack
npx tsx scripts/mcp-list-check.ts # verify tool discovery
npx tsx scripts/brand-cache-warm.ts # warm brand cacheTesting with MCP Inspector
npx @modelcontextprotocol/inspector npm run devThis launches the MCP Inspector UI where you can call tools interactively and verify responses.
Project Structure
agentflow-mcp/
├── src/
│ ├── index.ts # MCP server entry point (stdio + http-stream)
│ ├── tools/
│ │ ├── archPatternLookup.ts # Pattern matching + confidence scoring
│ │ ├── toolSelectionLookup.ts # Platform recommendation
│ │ ├── riskPolicyLookup.ts # Risk/governance checks + HITL
│ │ └── brandContextLookup.ts # Brandfetch + logo.dev with caching
│ ├── data/
│ │ ├── loader.ts # Source pack parser + in-memory index
│ │ ├── brandfetchClient.ts # Brandfetch Brand Context API client
│ │ ├── logoDevClient.ts # logo.dev Brand API client
│ │ └── brandCache.ts # Local file cache with TTL
│ └── types/
│ ├── source.ts # Source pack entry types
│ ├── arch-pattern.ts # arch_pattern_lookup types
│ ├── tool-selection.ts # tool_selection_lookup types
│ ├── risk-policy.ts # risk_policy_lookup types
│ └── brand-context.ts # brand_context_lookup types
├── data/ # Source pack (102 markdown files)
│ ├── industry/
│ ├── vendors/
│ └── patterns/
├── tests/ # Unit + integration tests
├── docs/ # PRD, MCP overview
├── scripts/ # Validation + cache warming scripts
├── openspec/ # OpenSpec specs (4 capabilities)
│ ├── specs/ # Main specs (synced from archived change)
│ └── changes/archive/ # Archived change proposals
├── Dockerfile # Multi-stage build for Fly.io
├── fly.toml # Fly.io app config
└── package.jsonTech Stack
Runtime: Node.js >= 20
MCP framework: MCP TypeScript SDK v2 (
@modelcontextprotocol/server2.x)Language: TypeScript (strict)
Validation: Zod v4
Linting/formatting: Biome
Testing: Node.js built-in test runner
Deployment: Docker + Fly.io
OpenSpec
This project uses OpenSpec for spec-driven development. The four tool capabilities are specified under openspec/specs/:
arch-pattern-lookup(7 requirements)brand-context-lookup(6 requirements)risk-policy-lookup(4 requirements)tool-selection-lookup(5 requirements)
Validate specs with:
openspec validate --specs
openspec doctorLicense
MIT
Available Tools
4 toolsarch_pattern_lookupA
Match an enterprise ask (industry, data stack, cloud, constraints) to a curated reference architecture pattern with components, data zones, integration notes, confidence, and diagram-ready data.
Inputs: industry (required), data_stack (required), constraints (required), cloud, +1 more.
brand_context_lookupA
Retrieve company brand context (name, description, tags, positioning, brand voice/style, logo URL) for a resolved domain, from Brandfetch plus logo.dev. Serves cached data when the sources are unavailable. Resolve partial company names to a domain before calling.
Inputs: domain (required).
risk_policy_lookupA
Return required controls, risk flags, and human-in-the-loop triggers for an architecture based on industry, data classification (PHI, PII, regulated financial data), region, deployment model, and governance constraints.
Inputs: region (required), industry (required), deployment (required), data_classification (required), +1 more.
tool_selection_lookupA
Recommend a data platform based on use case, data stack, constraints (HIPAA, PII, data residency, SSO/SAML), and latency needs — with cloud fit, reasoning, and alternatives.
Inputs: use_case (required), data_stack (required), constraints (required), latency.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct outcome: architecture pattern, brand info, platform recommendation, and risk controls. There is some conceptual overlap between architecture patterns and tool/risk recommendations, but the descriptions make their outputs clear enough to avoid major misselection.
All tool names follow the same clear `entity_lookup` pattern in lowercase snake_case: arch_pattern_lookup, brand_context_lookup, tool_selection_lookup, risk_policy_lookup. This makes the server feel uniform and predictable.
With only 4 focused lookup tools, the server is tightly scoped and does not introduce redundancy. Each tool serves a distinct functional need, making this an appropriate small toolset.
The server covers the major lookup categories it appears designed for: architecture, brand, platform, and policy. It is slightly limited by the lack of any listing or browsing endpoint for available patterns/platforms, but for a retrieval-oriented tool set the core coverage is strong.
Related MCP Connectors
Shared business knowledge, tools and skills for AI agents, with citations and approval controls.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Cloud or self-hosted knowledge for AI agents: hybrid search, reranking, GraphRAG, scoped MCP tools.
Your company's brain for AI agents. Cited, permission-aware knowledge across every system.
Related MCP Servers
AlicenseAqualityDmaintenanceProvides a persistent memory and governance layer that allows AI coding agents to query documented architecture rules and validate code against team standards. It enables agents to verify compliance across categories like security and testing before suggesting changes to ensure consistency across development sessions.317MIT- AlicenseNot gradedqualityDmaintenanceProvides comprehensive architectural expertise through specialized agents, resources, and tools for generating, evaluating, and modifying architectural designs.1,469 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query organizational architecture and governance constraints, returning evidence-grounded answers from documented structures.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with an embedded knowledge graph and architecture governance tools, enabling blast radius analysis, compliance checks, and smart context extraction from codebases.Apache 2.0