things-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 |
|---|---|
| add-todoD | – |
| add-projectD | – |
| updateD | – |
| update-projectD | – |
| showD | – |
| searchD | – |
| versionD | – |
| jsonD | – |
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
Several tools have ambiguous purposes: 'update' could apply to todos or projects, while 'show' and 'search' lack clear targets. 'add-todo' and 'add-project' are distinct, but the vague verbs make selection risky.
Naming patterns are inconsistent: some tools follow verb_noun (add-todo, add-project, update-project), but 'update', 'show', 'search' are bare verbs, and 'version' and 'json' are nouns. This mix makes it hard to predict tool names.
With 8 tools, the count is within a reasonable range and not overly heavy or thin. However, the inclusion of utility tools like 'version' and 'json' suggests some bloat relative to the apparent task-management domain.
The tool surface lacks essential operations such as delete or remove for todos and projects, and 'update' is too generic to cover specific update scenarios. The 'json' and 'version' tools do not contribute to domain coverage, leaving obvious gaps in lifecycle management.