idea-basin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IDEA_BASIN_URL | No | Base URL of your Idea Basin server | http://localhost:3500 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledgeA | Search the knowledge base using semantic similarity. Returns ranked chunks with source info. Use this to find relevant information before creating new resources. |
| browse_nodesA | Browse the knowledge graph structure. Returns the tree from a starting node (or root) with 3 levels of children. Use this to understand how knowledge is organized before searching or saving. |
| get_nodeA | Get detailed information about a specific node including its children and all resources. Use this to inspect what's already stored in a particular area of the knowledge graph. |
| save_resourceA | Save a new resource (note, research, link, code, idea) to a specific node in the knowledge graph. The content will be automatically chunked and embedded for future semantic search. |
| fetch_and_saveB | Fetch a URL, extract its content, and save it as a resource in the knowledge graph. The Basin server handles scraping (web pages, YouTube, GitHub, arXiv, PDFs) and automatic ingestion. |
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 serves a distinct purpose: navigating structure, ingesting external content, inspecting nodes, saving manual resources, and semantic search. There is no overlap in functionality.
All tools use consistent snake_case with verb_noun pattern (browse_nodes, fetch_and_save, get_node, save_resource, search_knowledge), making the API predictable.
With 5 tools, the server is well-scoped for knowledge graph management. Each tool is essential and the count is neither too few nor too many.
The set covers browsing, inspecting, adding (manual and fetched), and searching knowledge. Missing update/delete operations for nodes or resources, but these are not critical for core usage.