DrillSpark MCP Server

io.github.jackasserPublished by GitHub account jackasserv1.0.0Updated Oct 24, 2026

Create and manage Mermaid.js flowcharts and diagrams with AI agents via MCP.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant create and manage Mermaid.js flowcharts and diagrams through DrillSpark's hosted MCP endpoint.

What you can do
DrillSpark exposes a remote MCP endpoint for working with Mermaid.js flowcharts and diagrams. According to the registry description, it lets AI agents create and manage those diagrams. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Reach for it when you want an assistant to produce or maintain Mermaid.js diagrams as part of a documentation or design workflow, and you would rather use a hosted service than run diagram tooling locally. It is less suitable if you need offline operation or a documented list of specific diagram operations before installing.
Requirements
A remote MCP endpoint at using streamable HTTP; nothing is installed locally. Authentication is required via OAuth, with a bearer token supplied in the Authorization header (format Bearer dsk_xxxxx). Network access to the endpoint is needed.
Before you install
The server requires an OAuth credential sent as the Authorization header, described as a bearer token in the form Bearer dsk_xxxxx. Treat that token as a secret: anyone holding it can act on the DrillSpark account it belongs to. The description does not state whether diagram creation or editing overwrites or deletes existing content, so confirm that before pointing an assistant at shared diagrams.

Installation

In SourceWeft

  1. Open DrillSpark MCP Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jackasser%2Fdrillspark-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "drillspark": {
      "type": "http",
      "url": "https://drillspark.io/api/mcp/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.