Skip to main content
Glama
@quikrun/mcp

@quikrun/mcp

by exit150

@quikrun/mcp

A Model Context Protocol server for QuikRun. It lets an AI agent (Claude Desktop, Cursor, and other MCP clients) manage your QuikRun snippets — list, read, create, edit, run, deploy, duplicate, and delete — by wrapping the QuikRun REST API.

Requirements

  • Node.js 20 or newer

  • A QuikRun account and API token

Related MCP server: n8n MCP Server

Getting a token

  1. Sign in at quik.run.

  2. Go to Dashboard → Tokens.

  3. Mint a new token. It looks like quik_<keyId>_<secret>.

  4. Copy it — you will paste it into your MCP client config as QUIKRUN_TOKEN.

Claude Desktop setup

Add this to your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "quikrun": {
      "command": "npx",
      "args": ["-y", "@quikrun/mcp"],
      "env": {
        "QUIKRUN_TOKEN": "quik_yourKeyId_yourSecret"
      }
    }
  }
}

Restart Claude Desktop. The QuikRun tools appear in the tools menu.

Optional: self-hosted API

Point the server at a different QuikRun API host with QUIKRUN_API_URL (defaults to https://api.quik.run):

"env": {
  "QUIKRUN_TOKEN": "quik_yourKeyId_yourSecret",
  "QUIKRUN_API_URL": "https://api.quik.run"
}

Tools

Tool

What it does

list_snippets

List all your snippets with a compact summary.

get_snippet

Get one snippet's metadata and full source code.

create_snippet

Create a snippet (optional name, language, prompt).

update_snippet_code

Save source code to a snippet's draft.

run_snippet

Run a snippet and return output, response, and logs.

deploy_snippet

Publish the current draft as the live version.

update_snippet

Update name, visibility, language, or runtime.

duplicate_snippet

Duplicate a snippet.

delete_snippet

Permanently delete a snippet (destructive).

Development

npm install
npm run typecheck   # type-check without emitting
npm run build       # compile to dist/
npm run dev         # run from source with tsx

License

MIT

Available Tools

9 tools
create_snippetA

Create a new snippet. Optionally give it a name, language (defaults to javascript), and a prompt describing what it should do.

Inputs: name, prompt, language.

delete_snippetA

[DESTRUCTIVE] Permanently delete a snippet by slug. This cannot be undone.

Inputs: slug (required).

deploy_snippetA

Publish a snippet's current draft as the live version.

Inputs: slug (required).

duplicate_snippetA

Duplicate a snippet, returning the new snippet's slug and name.

Inputs: slug (required).

get_snippetA

Get one snippet's metadata and full source code by slug.

Inputs: slug (required).

list_snippetsA

List all of the user's QuikRun snippets with a compact summary (name, slug, language, visibility, endpoint, run count, last run).

Inputs: no named parameters.

run_snippetA

Run a snippet and return its output, HTTP response summary, and logs. Optionally override the request method, path, body, and bodyType, or run ad-hoc code.

Inputs: slug (required), body, code, path, +2 more.

update_snippetA

Update a snippet's settings: name, visibility (private|public), language, or runtime.

Inputs: slug (required), name, runtime, language, +1 more.

update_snippet_codeA

Save source code to a snippet's draft. Overwrites the current draft code.

Inputs: code (required), slug (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action or aspect of snippet management. There is minor potential confusion between update_snippet and update_snippet_code, but descriptions clearly differentiate settings updates from code updates. All other tools are unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_snippets, get_snippet, create_snippet, delete_snippet). The only minor deviation is list_snippets using plural, which is standard for collection operations. Overall, the pattern is highly predictable.

    Tool Count5/5

    With 9 tools, the server is well-scoped for snippet management. Each tool serves a necessary function in the lifecycle, and there is no redundancy or bloat.

    Completeness5/5

    The tool set covers the full snippet lifecycle: create, read, update (settings and code), delete, duplicate, run, and deploy. This provides complete coverage without any obvious gaps that would hinder typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers