hyperspell-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERSPELL_TOKEN | Yes | A valid user or app token (refer to the Hyperspell docs for how to obtain a user token) | |
| HYPERSPELL_COLLECTION | No | The name of the collection you want to query and add data to. If not set, it will use the user's default collection instead | |
| HYPERSPELL_USE_RESOURCES | No | Set to 'false' (default) to expose everything as tools, 'true' to expose retrieving single documents or listing collections as resources instead, or 'both' if you want it all | false |
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 |
|---|---|
| List CollectionsB | Get a list of all collections on Hyperspell |
| Get CollectionC | Get a list of all documents in a collection |
| Get DocumentC | Get a document from a collection |
| Search HyperspellC | Search Hyperspell for documents and data. |
| Add FileC | Add a file or website from a URL to Hyperspell. |
| Add MemoryC | Add a plain text document or memory to Hyperspell. |
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 6 tools
Each tool has a clearly distinct purpose: adding content (files/memories), retrieving collections/documents, and searching. No overlap exists, as tools target specific resources and actions like 'Add File' vs. 'Add Memory' or 'Get Collection' vs. 'Get Document'.
Naming is mixed with inconsistent patterns: 'Add File' and 'Add Memory' use verb-noun but with capital letters, while 'Get Collection', 'Get Document', 'List Collections', and 'Search Hyperspell' use verb-noun with varying capitalization and one tool including the server name. This makes it readable but lacks a uniform convention.
With 6 tools, the count is well-scoped for a document management server, covering core operations like adding, retrieving, listing, and searching without being too sparse or bloated. Each tool earns its place in the workflow.
The toolset covers essential CRUD-like operations for a document repository: adding content, retrieving collections/documents, and searching. Minor gaps exist, such as no update or delete tools, but agents can likely work around this for basic usage without significant failures.