MCP server for Capacities, a personal knowledge management system. Provides tools to list spaces, search content, save weblinks, create objects, and append to daily notes.
Server has 6 well-named tools with clear descriptions and Zod-validated schemas. All tools follow verb_noun naming (list_, get_, search_, save_, create_). Descriptions are substantive (100-200 chars, within baseline 194 avg). Input schemas are properly typed with Zod. However, output schemas are not documented, responses are JSON.stringify'd without field documentation, forcing LLMs to infer structure. Error handling is minimal (no recovery guidance, no categorization). Missing tool annotations (readOnlyHint/destructiveHint). Parameter descriptions are good but lack format constraints (e.g., spaceId format, URL validation present but not documented in description text).
Create a new object (page, note, or any custom type) in Capacities. Use get_space_info first to find available structureIds for the space.
Get detailed info about a space including structures (object types), collections, and property definitions. Needed to know which structureIds to use when creating objects.
List all personal Capacities spaces. Returns space IDs and names.
Append markdown content to today's daily note in a space. Great for quick captures, learning logs, and meeting notes.
Save a URL as a weblink object in Capacities. Supports tags, custom title, description, and markdown notes.
Search content across Capacities spaces. Returns matching object titles and IDs (not full content, API limitation).
Output schemas not documented. All tools return JSON.stringify'd responses without field documentation. LLMs cannot infer what fields to expect or plan downstream calls.
No tool annotations (readOnlyHint/destructiveHint). Write tools (save_weblink, save_to_daily_note, create_object) lack destructiveHint=true, preventing agents from understanding side effects.
Error handling lacks recovery guidance. CapacitiesApiError provides friendly messages but no actionable next steps (e.g., 'Try search_spaces() first' or 'Rate limit: retry in 60s').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2026-07-28+ | v2 |
Parameter descriptions lack format constraints. 'spaceId' description does not specify format (UUID? alphanumeric?). 'mdText' lacks length limits. Constraints should be in description text, not just schema.
No pagination support. search() and list_spaces() may return large result sets without limit/offset/cursor parameters, risking context window exhaustion.