
DrillSpark MCP Server
Wire your coding agent to create, update, and organize Mermaid flowcharts and architecture diagrams in DrillSpark without leaving the chat.
Overview
DrillSpark MCP is a MCP server for the Build phase that lets AI agents create and manage Mermaid.js flowcharts and diagrams in DrillSpark over streamable HTTP.
What is this MCP server?
- Streamable HTTP MCP remote at drillspark.io with Bearer dsk_* API authentication
- Create and manage Mermaid.js flowcharts and diagrams from Claude Code, Cursor, or Codex
- Centralized diagram lifecycle on DrillSpark instead of scattered markdown-only charts in repos
- Documented setup at drillspark.io docs for MCP registration
- Backed by the flowMind GitHub repository (jackasser/flowMind)
- MCP server schema version 1.0.0
- Single streamable-http remote endpoint
- Required secret Authorization header (Bearer dsk_xxxxx)
What problem does it solve?
Keeping architecture and process diagrams in sync with fast-moving code is tedious when agents can only edit text files and cannot touch a real diagram editor.
Who is it for?
Solo builders who use Claude Code or Cursor daily and want agent-driven Mermaid diagrams stored in DrillSpark for specs and onboarding.
Skip if: Teams that need offline-only, git-native diagram workflows with no hosted account or API key.
What do I get? / Deliverables
After you register the remote with a DrillSpark API token, your agent can maintain live Mermaid diagrams in DrillSpark alongside your build and documentation work.
- Agent-created and updated Mermaid flowcharts in DrillSpark
- Centralized diagram set for specs and onboarding
- MCP remote configuration with authenticated headers
Recommended MCP Servers
Journey fit
How it compares
Hosted DrillSpark diagram MCP, not a standalone local Mermaid snippet skill in your repo.
Common Questions / FAQ
Who is DrillSpark MCP for?
Indie developers and small teams who document systems with Mermaid and want their AI coding agent to create and update those diagrams in DrillSpark through MCP.
When should I use DrillSpark MCP?
Use it during Build when you are writing architecture docs, user flows, or runbooks and want the agent to generate or revise Mermaid charts in a managed workspace instead of hand-editing diagrams.
How do I add DrillSpark MCP to my agent?
Add the streamable HTTP remote https://drillspark.io/api/mcp/mcp to your MCP client and set the Authorization header to Bearer plus your DrillSpark API key (dsk_xxxxx); see drillspark.io MCP docs for client-specific steps.