Capacities MCP Bridge (Unofficial)
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_space_infoC | Get structures and collections of a space |
| get_spacesA | Get your spaces |
| save_to_daily_noteC | Save text to today's daily note |
| save_weblinkC | Save a weblink to a space |
| search_contentD | Search for content |
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 5 tools
Each tool targets a distinct action and resource: list spaces, get space details, save text to daily note, save weblink, and search. There is no overlap or ambiguity between tool purposes.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., get_spaces, save_to_daily_note, search_content). The naming style is uniform and predictable.
5 tools is well-scoped for a lightweight bridge. It provides core read, write, and search capabilities without unnecessary redundancy or bloat.
The toolset covers essential workflows: retrieving spaces, saving content, and searching. Minor gaps exist such as lack of general note creation or update/delete operations, but these are acceptable for an unofficial bridge.