Skip to main content
Glama
idea-basin-mcp
by MsFixer101

idea-basin-mcp

MCP server for Idea Basin — a semantic knowledge graph with vector search, hierarchical organization, and automatic content ingestion.

Gives Claude (and any MCP-compatible AI assistant) the ability to search, browse, and save to your personal knowledge base.

How it works

flowchart LR
    subgraph client["AI Assistant"]
        Claude["Claude / Any MCP Client"]
    end

    subgraph mcp["idea-basin-mcp"]
        direction TB
        T1["search_knowledge"]
        T2["browse_nodes"]
        T3["get_node"]
        T4["save_resource"]
        T5["fetch_and_save"]
    end

    subgraph basin["Idea Basin Server :3500"]
        API["REST API"]
        Embed["Embedder"]
        Scraper["Scraper"]
    end

    subgraph storage["Storage"]
        PG[("PostgreSQL + pgvector")]
    end

    Claude -- "stdio / JSON-RPC" --> mcp
    mcp -- "HTTP" --> API
    API --> Embed
    API --> Scraper
    API --> PG

Related MCP server: supermem

Tools

Tool

Description

search_knowledge

Semantic similarity search across all knowledge chunks

browse_nodes

Browse the knowledge graph tree structure (3 levels deep)

get_node

Inspect a node with its children and resources

save_resource

Save a note, research, link, code, or idea to a node

fetch_and_save

Fetch a URL (web page, YouTube, GitHub, arXiv, PDF) and save it

Prerequisites

A running Idea Basin server (default: http://localhost:3500).

Install

Claude Code

claude mcp add idea-basin -- node /path/to/idea-basin-mcp/build/index.js

Or with a custom Basin URL:

claude mcp add idea-basin -e IDEA_BASIN_URL=http://localhost:3500 -- node /path/to/idea-basin-mcp/build/index.js

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "idea-basin": {
      "command": "node",
      "args": ["/path/to/idea-basin-mcp/build/index.js"],
      "env": {
        "IDEA_BASIN_URL": "http://localhost:3500"
      }
    }
  }
}

npm (once published)

npx idea-basin-mcp

Configuration

Env var

Default

Description

IDEA_BASIN_URL

http://localhost:3500

Base URL of your Idea Basin server

Development

npm install
npm run build    # TypeScript → build/
npm run dev      # Watch mode

License

MIT

Available Tools

5 tools
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.

Inputs: node_id.

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.

Inputs: url (required), node_id (required), why.

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.

Inputs: node_id (required).

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.

Inputs: node_id (required), type (required), content (required), description, +2 more.

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.

Inputs: query (required), node_id, limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.
      14
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables storing and querying a personal knowledge graph as a shared memory, allowing agents and tools to remember facts, entities, relations, and recall relevant context via natural language hybrid search.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables teams to capture and distill knowledge from sessions, meetings, and feeds into a searchable, vector-embedded graph, then retrieve or synthesize it conversationally via semantic search and citations.
      17
      25
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to capture bookmarks, sticky notes, todos, notes, and web archives, and to search and organize personal knowledge and memory across cloud-synced clients.
      -