negative-support-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEGATIVE_SUPPORT_TOKEN | No | Your negative.support token (ns_live_...). Optional; if omitted, use the negative_support_activate tool once per session. |
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
} |
| logging | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| negative_support_activateA | Activate a negative.support license for this MCP process. Same ns_live_* token as the CLI. Alternatively set env NEGATIVE_SUPPORT_TOKEN. |
| negative_support_deactivateA | Clear the active license in this process (does not revoke the token on the server). |
| negative_support_generateA | Generate support STL (and optionally 3MF with model + support pieces) from a local STL, OBJ, STEP, or STP file. Requires an activated license. Heavy meshes can take many minutes; MCP hosts that send a progressToken receive keepalive progress and avoid tool timeouts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| negative-support-documentation | Summary of the negative-support API; see https://negative.support/docs for full reference |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: activation, deactivation, and generation. There is no overlap or ambiguity between them.
All tool names follow the same pattern: 'negative_support_' prefix plus a clear verb (activate, deactivate, generate). The convention is consistent and predictable.
With 3 tools, the set is tightly scoped to the server's purpose of license management and STL generation. Each tool earns its place with no redundancy.
The core lifecycle is covered: activate a license, deactivate it, and generate output. No obvious missing operations for the stated domain.