@quikrun/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_snippetsA | List all of the user's QuikRun snippets with a compact summary (name, slug, language, visibility, endpoint, run count, last run). |
| get_snippetA | Get one snippet's metadata and full source code by slug. |
| create_snippetA | Create a new snippet. Optionally give it a name, language (defaults to javascript), and a prompt describing what it should do. |
| update_snippet_codeA | Save source code to a snippet's draft. Overwrites the current draft code. |
| 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. |
| deploy_snippetA | Publish a snippet's current draft as the live version. |
| update_snippetA | Update a snippet's settings: name, visibility (private|public), language, or runtime. |
| duplicate_snippetA | Duplicate a snippet, returning the new snippet's slug and name. |
| delete_snippetA | [DESTRUCTIVE] Permanently delete a snippet by slug. This cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.