masscode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MASSCODE_PORT | No | Port massCode's local API is listening on. Default is 4321. | 4321 |
| MASSCODE_API_KEY | No | Bearer token, if your massCode build requires one. Optional. |
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 |
|---|---|
| masscode_list_snippetsA | Search or list snippets from MassCode. Optionally filter by search query, folderId, or tagId. |
| masscode_get_snippetA | Get a single snippet by its ID, including all content fragments. |
| masscode_create_snippetA | Create a new snippet in MassCode. |
| masscode_update_snippetA | Update an existing snippet by ID. Only provide fields you want to change. |
| masscode_list_foldersA | List all snippet folders as a tree structure. |
| masscode_create_folderB | Create a new snippet folder. |
| masscode_list_tagsA | List all tags in MassCode. |
| masscode_create_tagC | Create a new tag. |
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 8 tools
Each tool targets a distinct resource (snippet, folder, tag) and action (create, list, get, update). No two tools have overlapping purposes; list_snippets and get_snippet are clearly differentiated by search/list vs single-fetch by ID.
All tools follow a consistent snake_case pattern of masscode_<verb>_<noun>, with verbs limited to create, list, get, and update. The naming is uniform and predictable.
Eight tools is an appropriate size for a snippet management server. Each tool serves a clear function and covers the main resources without unnecessary bloat or missing essentials.
The set provides create, read, and update for snippets, but lacks delete operations for snippets, folders, and tags. Folders and tags only support create and list, leaving update and delete holes. These are notable gaps for a comprehensive snippet management tool.