Resurgo-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESURGO_API_KEY | Yes | Your Resurgo API key for authentication | |
| RESURGO_API_URL | No | Optional: Override the API URL for self-hosted instances |
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 |
|---|---|
| search_nodesC | Search saved nodes with full-text and semantic search |
| get_due_itemsC | Get items due for review (inbox items) |
| quick_captureC | Save a new node with optional scheduling |
| snooze_nodeC | Defer resurfacing to a later date |
| complete_nodeB | Mark a node as done |
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 has a clearly distinct purpose with no overlap: complete_node marks nodes as done, get_due_items retrieves due items, quick_capture saves new nodes, search_nodes searches existing nodes, and snooze_node defers resurfacing. The descriptions make it easy to distinguish between creation (quick_capture), retrieval (get_due_items, search_nodes), and modification (complete_node, snooze_node) operations.
All tools follow a consistent verb_noun naming pattern with snake_case: complete_node, get_due_items, quick_capture, search_nodes, and snooze_node. The verbs are clear and appropriate (complete, get, capture, search, snooze), and the nouns consistently refer to nodes or items, creating a predictable and readable set.
With 5 tools, this server is well-scoped for managing nodes/items in a productivity or note-taking system. Each tool earns its place by covering core operations: capture (quick_capture), retrieval (get_due_items, search_nodes), and status updates (complete_node, snooze_node). The count is neither too thin nor bloated, fitting typical workflows efficiently.
The tool set provides strong coverage for a node management system, including creation, retrieval, and modification (completion and deferral). A minor gap exists in update operations for node content or metadata beyond scheduling, but agents can work around this by capturing new nodes. Core workflows like inbox review and search are well-supported, with no dead ends.