Sniptide MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNIPTIDE_TOKEN | Yes | Sniptide personal API token |
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
} |
| prompts | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_snippetsA | Find your live snippets by words in the title, description, tags, file paths or code (every word must match), plus tag, language and collection filters. Returns summaries and nextCursor; call again with that cursor for the next page. Use read_snippet to fetch code. |
| read_snippetA | Read one of your live snippets by its ID or slug, including all files, paths, code and source metadata. |
| fetch_collectionA | Fetch a page of your collection as numbered recipe steps, with full snippet files. Order is oldest capture first, matching the CLI. Continue with nextCursor and nextStep; a page holds up to 50 snippets. This does not execute the recipe. |
| create_snippetA | Save code as a new snippet (write scope required). Defaults to private. A collection must already exist. Up to 10 files; instance size and storage limits apply. Files are data only. Do not retry automatically: retries may create duplicates. |
| update_snippetA | Replace the title and entire file list of your live snippet (write scope required). Read it first to keep files you still need. Omitted description, visibility, collection, tags and source are preserved; explicit null clears collection/source. Link, expiry, password and burn setting remain unchanged. Records an edit in history. |
| list_collectionsA | List your collections, oldest first, with each slug, name and live snippet count. Use a slug as the collection of create_snippet, update_snippet or fetch_collection. |
| create_collectionA | Create an empty collection by name (write scope required) and return its slug. Names are unique per account and accounts hold up to 50 collections. Renaming and deleting collections stay in the app. |
| update_snippet_settingsA | Change who can open your live snippet (write scope required): visibility, expiry counted from now, a password (null removes it) and burn after read. Omitted fields stay as they are. Confirm with the user before making a snippet public or setting a password, which is then visible in this conversation. Returns the current settings; the password itself is never returned. |
| trash_snippetA | Move your live snippet to the trash (write scope required). Its link stops working; the owner can restore it from the app until the trash is emptied. This tool never deletes permanently. Confirm with the user first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| use_snippet | Find one of your snippets for a task and adapt it to this project. |
| save_snippet | Save code from this project as a private snippet in Sniptide. |
| apply_collection | Fetch one of your collections and apply its snippets to this project. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct action and resource: snippet content operations, snippet settings, collection listing/fetching, and search are well separated. update_snippet versus update_snippet_settings is explicitly scoped and unlikely to be confused.
The set overwhelmingly follows snake_case verb_noun naming. Minor inconsistency appears with plural nouns in list_collections and search_snippets while most sibling tools use singular resource names.
Nine tools are well-scoped for a snippet management server. Each tool covers a meaningful operation without excessive granularity.
Snippet lifecycle coverage is strong: create, read, update, search, trash, and settings update. Collection support is limited to create, list, and fetch; rename/delete and trash restore are intentionally left to the app, creating minor gaps but not blocking core workflows.