Convolut MCP Server
Provides support channel access through Discord for troubleshooting and community assistance
Hosts the project repository and issue tracking for the MCP server
Supports exporting contexts to Markdown format for documentation and sharing
Runs as a Node.js application providing the MCP server runtime environment
Distributed through npm package registry for easy installation and updates
Supports exporting contexts to XML format for structured data representation
Click on "Deploy 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., "@Convolut MCP Server search for contexts about AI 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.
Convolut MCP Server
Official Model Context Protocol (MCP) server for Convolut Context Bank, enabling seamless integration with Claude Desktop and other MCP clients.
Features
š 11 Powerful Tools for context management and AI-powered operations:
Context Management
list_contexts- Search and filter contexts with advanced optionsget_context- Retrieve specific context by IDcreate_context- Create new context with content and metadataupdate_context- Update existing contextsdelete_context- Delete contexts by ID
AI-Powered Operations
search_contexts- Semantic search across your contextsconsolidate_contexts- AI-powered context consolidation and summarizationplan_from_contexts- Generate actionable plans from multiple contexts
Export & Integration
export_contexts- Export to JSON, XML, TXT, or Markdown formatsget_raw_url- Generate temporary shareable URLsget_context_stats- Statistical analysis of your contexts
Related MCP server: MyChatArchive MCP Server
Quick Start
Installation
npm install -g @convolut/convolut-mcpClaude Desktop Setup
Get your Convolut API key from https://convolut.app
Add to your Claude Desktop configuration file:
Windows: %APPDATA%\\Claude\\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"convolut": {
"command": "npx",
"args": ["@convolut/convolut-mcp"],
"env": {
"CONVOLUT_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Desktop
Start using Convolut tools in your conversations! š
Usage Examples
Search Your Contexts
"Search for contexts about machine learning"Claude will use the search_contexts tool to find relevant contexts in your Convolut library.
Create New Context
"Save this conversation as a new context titled 'API Integration Discussion'"Claude will use create_context to save the conversation to your Convolut account.
Generate Plans
"Analyze these project contexts and create an actionable plan"Claude will use consolidate_contexts and plan_from_contexts to analyze multiple contexts and generate structured plans.
Manual Installation
If you prefer to install locally:
# Clone or download the package
git clone https://github.com/expdal3/convolut-mcp.git
cd convolut-mcp
# Install dependencies (none required - pure Node.js!)
npm install
# Test the installation
CONVOLUT_API_KEY=your_key_here node stdio-client.cjsThen use the full path in your Claude Desktop config:
{
"mcpServers": {
"convolut": {
"command": "node",
"args": ["/full/path/to/convolut-mcp/stdio-client.cjs"],
"env": {
"CONVOLUT_API_KEY": "your_api_key_here"
}
}
}
}API Key Setup
Get Your API Key
Sign up at https://convolut.app
Navigate to Settings ā API Keys
Generate a new API key
Copy the key (format:
convolut_sk_...)
Environment Variables
You can also set the API key as an environment variable:
# Windows
set CONVOLUT_API_KEY=your_api_key_here
# macOS/Linux
export CONVOLUT_API_KEY=your_api_key_hereArchitecture
Claude Desktop (or other MCP Client) ā stdio ā convolut-mcp (MCP Server) ā HTTPS ā api.convolut.appThis MCP server provides a direct, efficient bridge between Claude Desktop and the Convolut API, with no intermediate servers required.
Requirements
Node.js 18.0.0 or higher
Convolut API key
Claude Desktop (or any MCP-compatible client)
Supported Platforms
ā Windows 10/11
ā macOS 12+
ā Linux (Ubuntu 20.04+)
Troubleshooting
Claude Desktop Not Seeing Tools
Verify your
claude_desktop_config.jsonsyntax is correctCheck that your API key is valid
Restart Claude Desktop completely
Check Claude Desktop logs for errors
API Key Issues
Error: CONVOLUT_API_KEY environment variable is requiredEnsure your API key is set in the Claude Desktop config
Verify the API key format starts with
conair_sk_Check for typos in the configuration file
Connection Issues
Verify internet connectivity
Check if your firewall blocks HTTPS requests
Ensure Node.js version is 18.0.0 or higher
Development
Project Structure
convolut-mcp/
āāā stdio-client.cjs # Main MCP server entry point
āāā utils/
ā āāā api-client.cjs # Convolut API client
āāā tools/
ā āāā contexts.cjs # Context management tools
ā āāā ai-tools.cjs # AI-powered operations
ā āāā export.cjs # Export and statistics
āāā types/
ā āāā convolut.cjs # Type definitions
āāā README.mdContributing
Fork the repository
Create a feature branch
Make your changes
Test thoroughly
Submit a pull request
License
MIT License - see LICENSE file for details.
Support
Documentation: https://docs.convolut.app/mcp
Discord: https://discord.gg/convolut-ai
Related Projects
Convolut Web App - Main context management platform
Convolut API Documentation - REST API reference
MCP Specification - Model Context Protocol standard
Made with ā¤ļø by the Convolut team
Available Tools
11 toolsconsolidate_contextsC
Merge multiple contexts using AI to create a consolidated summary or composition
Inputs: context_ids (required), consolidation_type (required), custom_prompt.
create_contextC
Create a new context with title, content, tags, and metadata
Inputs: title (required), content (required), tags, category, +2 more.
delete_contextC
Delete a context permanently by its ID
Inputs: context_id (required).
export_contextsC
Export contexts in various formats (JSON, XML, TXT, Markdown) for integration with other systems
Inputs: context_ids (required), format (required), include_metadata.
get_contextB
Retrieve a specific context by its ID, including full content and metadata
Inputs: context_id (required).
get_context_statsB
Get statistical information about contexts including counts, categories, and usage metrics
Inputs: date_range, group_by.
get_raw_urlA
Generate a temporary raw URL for a context that can be accessed without authentication (expires in 10 minutes)
Inputs: context_id (required).
list_contextsC
Search and filter contexts with advanced options including keywords, tags, categories, and date ranges
Inputs: limit, offset, contain, category, +4 more.
plan_from_contextsC
Analyze contexts and generate actionable plans using AI
Inputs: context_ids (required), planning_prompt.
search_contextsC
Perform semantic search across contexts to find relevant information
Inputs: query (required), limit, category, tags.
update_contextC
Update an existing context with new title, content, tags, or metadata
Inputs: context_id (required), title, content, tags, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, create_context, get_context, update_context, and delete_context form distinct CRUD operations, while consolidate_contexts, plan_from_contexts, and search_contexts each serve unique AI-driven functions. The descriptions clearly differentiate overlapping tools like list_contexts (filtering) and search_contexts (semantic search).
All tool names follow a consistent verb_noun pattern using snake_case, such as create_context, delete_context, and get_context_stats. There are no deviations in naming conventions, making the set predictable and readable. This uniformity aids in agent selection and understanding of tool purposes.
With 11 tools, the count is well-scoped for a context management server, covering core operations without bloat. Each tool earns its place by addressing specific needs like CRUD, search, export, and AI analysis. This aligns with typical server scopes of 3-15 tools, ensuring comprehensive coverage without overwhelming complexity.
The tool surface provides complete CRUD/lifecycle coverage for context management, including create, get, update, delete, list, and search. It extends beyond basics with AI features (consolidate, plan), utilities (export, raw URL), and analytics (stats), leaving no obvious gaps. Agents can perform end-to-end workflows without dead ends.
Maintenance
Related MCP Connectors
Your portable context layer ā load it into any AI.
Intelligent context infrastructure for AI teams: knowledge graph, sessions, tasks, documents.
Enterprise memory, search, and context for frontier AI. 38 tools for business intelligence.
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Logseq knowledge graphs to read, write, and search pages, blocks, and journals via the Model Context Protocol. It features 17 tools for full graph management, including CRUD operations, batch block insertion, and full-text search.23 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables semantic search across your local AI conversation history (ChatGPT, Claude, etc.) and provides tools to retrieve context, capture thoughts, and get profile summaries.72AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables storing, searching, and compressing contextual memories for LLM interactions, with tools for memory management and context injection.9MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to search, retrieve, and manage documents from a Context11 knowledge base through tools like search_context, get_document, and list_folders.611 npmMIT