Heptabase MCP
The Heptabase MCP server enables AI assistants to interact with Heptabase backup data through multiple functions:
Backup Management: Configure paths, list available backups, and load specific backups
Search Operations: Find whiteboards and cards using queries, filters, tags, and date ranges
Data Retrieval: Access whiteboard and card data, including cards within specific areas
Export Functions: Export content to Markdown, JSON, and HTML formats
Analysis Tools: Analyze card relationships, compare backups, and evaluate graph metrics
Summaries: Generate whiteboard summaries
Debugging: Access server state information for troubleshooting
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Heptabase MCPsearch for whiteboards about project planning"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@heptabase/mcp
A Model Context Protocol (MCP) service for interacting with Heptabase backup data. This service allows AI assistants like Claude to search, retrieve, analyze, and export Heptabase whiteboards and cards.
Features
🔍 Search whiteboards and cards
📁 Automatic backup file management
📄 Export to multiple formats (Markdown, JSON, Mermaid)
🔗 Analyze card relationships
📊 Generate whiteboard summaries
⚡ Smart caching for performance
Related MCP server: Logseq MCP Tools
Quick Start
Installation and Setup
Clone and install:
git clone <repository-url> cd heptabase-mcp npm installConfigure using environment variables:
cp .env.example .env # Edit .env with your actual pathsBuild the project:
npm run buildTest locally (optional):
npm start
Using with Claude Desktop
Configure Claude Desktop to use your local build:
Edit your Claude Desktop config file:
macOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Add this configuration:
{
"mcpServers": {
"heptabase": {
"command": "/path/to/node",
"args": ["/path/to/your/heptabase-mcp/dist/index.js"],
"env": {
"HEPTABASE_BACKUP_PATH": "/path/to/your/heptabase/backups",
"HEPTABASE_AUTO_EXTRACT": "true",
"HEPTABASE_WATCH_DIRECTORY": "true"
}
}
}
}Important:
Replace
/path/to/nodewith your Node.js path (find withwhich node)Replace
/path/to/your/heptabase-mcpwith your actual project pathSet
HEPTABASE_BACKUP_PATHto your Heptabase backup directory
See QUICK_START.md for detailed setup instructions.
Configuration
This project uses a privacy-safe configuration system:
Example files (safe for git):
claude-config-example.json,.env.examplePersonal files (gitignored):
claude-config-*personal*.json,.env
See CONFIG.md for detailed configuration instructions.
Basic Usage
// Configure backup path
await mcpClient.callTool({
name: "configureBackupPath",
parameters: {
path: "/path/to/your/heptabase/backups"
}
});
// List available backups
const backups = await mcpClient.callTool({
name: "listBackups"
});
// Search for whiteboards
const whiteboards = await mcpClient.callTool({
name: "searchWhiteboards",
parameters: {
query: "Project Planning"
}
});
// Get full whiteboard content
const whiteboard = await mcpClient.callTool({
name: "getWhiteboard",
parameters: {
whiteboardId: "your-whiteboard-id",
includeCards: true,
includeConnections: true
}
});
// Export to markdown
const markdown = await mcpClient.callTool({
name: "exportWhiteboard",
parameters: {
whiteboardId: "your-whiteboard-id",
format: "markdown"
}
});Available Tools
Backup Management
configureBackupPath- Set backup directorylistBackups- List available backupsloadBackup- Load a specific backup
Search Operations
searchWhiteboards- Search whiteboards by name or contentsearchCards- Search cards across all whiteboards
Data Retrieval
getWhiteboard- Get complete whiteboard datagetCard- Get card content in multiple formatsgetCardContent- Get card content as resource (bypasses size limits)getCardsByArea- Find cards by position on whiteboard
Export Functions
exportWhiteboard- Export to Markdown, JSON, HTML formatssummarizeWhiteboard- Generate AI-powered summaries
Analysis Tools
analyzeGraph- Analyze card relationships and connectionscompareBackups- Compare different backup versions
Debug Tools
debugInfo- Get system status and diagnostics
Development
Project Structure
heptabase-mcp/
├── src/
│ ├── index.ts # Main entry point
│ ├── server.ts # MCP server implementation
│ ├── services/ # Core business logic
│ │ ├── BackupManager.ts # Backup file management
│ │ └── HeptabaseDataService.ts # Data querying
│ ├── tools/ # MCP tool implementations
│ ├── types/ # TypeScript definitions
│ └── utils/ # Helper functions
├── tests/ # Test suites
├── docs/ # Documentation
└── config files # Configuration templatesTesting
# Run all tests
npm test
# Run tests in watch mode
npm run test:watch
# Run with coverage
npm run test:coverage
# Run integration tests
npm run test:integrationBuilding
# Build for production
npm run build
# Development mode with auto-reload
npm run dev
# Type checking only
npm run type-checkDocumentation
📚 Complete Specification - Detailed API and architecture
🚀 Quick Start Guide - Get up and running fast
⚙️ Configuration Guide - Safe configuration practices
📖 Claude Desktop Setup - Local development setup
Privacy & Security
This project follows privacy-by-design principles:
✅ Personal paths are never committed to git
✅ Backup data stays local on your machine
✅ Configuration templates use safe placeholders
✅ Gitignore protects sensitive files
Requirements
Node.js 18+
Heptabase with backup exports enabled
Claude Desktop (for MCP integration)
Troubleshooting
Common Issues
"No backups found" - Check your
HEPTABASE_BACKUP_PATHpoints to the correct directory"Command not found" - Ensure Node.js is installed and paths are correct
Claude doesn't see tools - Restart Claude Desktop completely after config changes
Build errors - Run
npm installandnpm run buildbefore using
Debug Mode
Use the debugInfo tool to check system status:
await mcpClient.callTool({ name: "debugInfo" });Contributing
Contributions are welcome! Please:
Fork the repository
Create a feature branch
Make your changes
Add tests for new functionality
Ensure all tests pass
Submit a pull request
See SPECIFICATION.md for architecture details.
License
MIT License - see LICENSE file for details.
Support
🐛 Bug reports: GitHub Issues
💬 Questions: GitHub Discussions
📧 Security issues: Please report privately
Made with ❤️ for the Heptabase community
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol implementation that enables AI assistants to interact with markdown documentation files, providing capabilities for document management, metadata handling, search, and documentation health analysis.146058MIT
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that provides AI assistants with structured access to your Logseq knowledge graph, enabling retrieval, searching, analysis, and creation of content within your personal knowledge base.70
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with full-text search access to your Obsidian vault, allowing them to query, retrieve, and analyze notes through the Model Context Protocol.3
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Obsidian vaults through vector search, vault indexing, and file monitoring. It provides a standardized interface for searching and managing markdown-based personal knowledge management data within the Model Context Protocol.5,7841MIT
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LarryStanley/heptabase-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server