DrillSpark MCP Server
- jackasser/flowMind
DrillSpark MCP is a MCP server that lets AI agents create and manage Mermaid.js flowcharts and diagrams in DrillSpark over streamable HTTP.
About
DrillSpark MCP Server exposes DrillSpark’s diagram workspace to AI assistants through the Model Context Protocol, so developers can ask an agent to draft or revise Mermaid flowcharts, sequence diagrams, and other Mermaid.js visuals and keep them in a managed DrillSpark project. It fits developers who document APIs, onboarding, and system design in the same sprint where they ship features, and who want the agent to iterate on diagrams without manual export/import loops. You register the remote MCP endpoint with a required Authorization header (Bearer token format dsk_xxxxx), then drive create-and-manage operations from natural language. This is an MCP integration to a hosted diagram service, not a local-only Mermaid rendering skill; pair it with your repo’s markdown when you need diagrams checked into git as source of truth.
- 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)
DrillSpark MCP Server by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http drillspark-mcp https://drillspark.io/api/mcp/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Repository | jackasser/flowMind ↗ |
What it does
Wire your coding agent to create, update, and organize Mermaid flowcharts and architecture diagrams in DrillSpark without leaving the chat.
Who is it for?
Best when you use Claude Code or Cursor daily and want agent-driven Mermaid diagrams stored in DrillSpark for specs and onboarding.
Skip if: Skip if you need offline-only, git-native diagram workflows with no hosted account or API key.
What you get
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
By the numbers
- MCP server schema version 1.0.0
- Single streamable-http remote endpoint
- Required secret Authorization header (Bearer dsk_xxxxx)
Recommended MCP Servers
0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.
123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stayHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
Hosted DrillSpark diagram MCP, not a standalone local Mermaid snippet skill in your repo.
FAQ
Who is DrillSpark MCP for?
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.