Capacities-MCP-Plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPACITIES_API_KEY | Yes | Your Capacities API key (get it from your Capacities account settings at https://capacities.io/) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capacities_list_spacesB | Get a list of all personal spaces in Capacities |
| capacities_get_space_infoA | Get detailed information about a specific Capacities space including structures and collections |
| capacities_searchA | Search for content across Capacities spaces with optional filtering |
| capacities_read_object_contentA | Retrieve the full content of a Capacities object by its ID. Optionally provide a title or search term to improve results. This tries undocumented endpoints first, then falls back to search API aggregation. |
| capacities_save_weblinkA | Save a web link to a Capacities space with optional title and tags |
| capacities_save_to_daily_noteB | Add markdown text to today's daily note in a Capacities space |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| capacities-daily-summary | Create a structured daily summary for your Capacities daily note |
| capacities-research-note | Format research findings for saving to Capacities |
| capacities-meeting-notes | Structure meeting notes for Capacities daily note |
| capacities-job-application | Generate a Capacities-ready markdown file for tracking job applications. Creates properly formatted YAML frontmatter and structure for import into Capacities. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: get_space_info, list_spaces, read_object_content, save_to_daily_note, save_weblink, and search. However, read_object_content and search could potentially overlap in some retrieval scenarios, though their descriptions help differentiate them (one retrieves specific object content, the other searches across spaces).
All tools follow a consistent naming pattern: 'capacities_' prefix followed by a descriptive verb_noun combination (e.g., get_space_info, list_spaces, read_object_content). This makes the tool set predictable and easy to understand at a glance.
With 6 tools, this server is well-scoped for its purpose of interacting with Capacities spaces. Each tool serves a distinct function (info retrieval, listing, content reading, saving notes/links, and searching), and none feel redundant or unnecessary for the domain.
The tool set covers core operations for the Capacities domain: reading (get_space_info, list_spaces, read_object_content, search) and writing (save_to_daily_note, save_weblink). A minor gap is the lack of update or delete operations for objects, but agents can likely work around this given the focus on retrieval and basic saving.