ultrathink-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ULTRATHINK_SOURCE | No | Optional. Tag entries with a source label (e.g., claude-code). | |
| ULTRATHINK_API_BASE | No | Optional. The Ultrathink API base URL. Defaults to https://us-central1-ultrathink-50f7f.cloudfunctions.net. | |
| ULTRATHINK_DEVICE_KEY | Yes | Your Ultrathink device key. Get one at https://tryultrathink.com. |
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 |
|---|---|
| ultrathink_saveB | Save an entry to Ultrathink knowledge base. Use this to store notes, ideas, links, snippets, and other knowledge. |
| ultrathink_searchA | Search the Ultrathink knowledge base using natural language. Returns an AI-generated answer based on stored entries. |
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 2 tools
The two tools perform clearly opposite, non-overlapping operations: write (save) and read (search). An agent can instantly choose between storing knowledge and retrieving it, with no ambiguity.
Both tools follow an identical pattern: the `ultrathink_` namespace prefix plus a concise verb (save, search). Fully predictable and consistent.
Two tools is on the thin side for a knowledge base server; a minimal capture-and-retrieve surface works, but there is little else an agent can do. It sits at the borderline of under-scoped.
Core store-and-query flow is covered, but obvious knowledge-management operations are absent: no update, delete, list/recent entries, or get-by-id. Agents cannot correct or manage stored entries, only add and search.