This document provides installation instructions for AI assistants (Cline, Claude Desktop, Cursor, Antigravity, and other MCP clients) to automatically set up Pomera AI Commander as an MCP server.
Pomera AI Commander is an MCP server providing 24+ deterministic text processing tools that reduce token usage by 70-80% for common agentic AI workflows.
Key Benefits:
- ✅ No API keys required (works offline, privacy-focused)
- ✅ Session persistence via Notes system (cross-conversation memory)
- ✅ Token efficiency - Deterministic operations outside context window
- ✅ Universal compatibility - Works with all MCP clients
Top 10 Critical Tools:
pomera_notes- Persistent memory with FTS5 search (prevents re-pasting)pomera_web_search- 7-engine web search (Tavily/Exa/Brave/Google/DuckDuckGo)pomera_read_url- Fetch & convert HTML to markdownpomera_find_replace_diff- Regex with diff preview & auto-backuppomera_smart_diff_2way- Semantic config diff (JSON/YAML/ENV/TOML)pomera_smart_diff_3way- 3-way merge with conflict resolutionpomera_ai_tools- Multi-provider AI delegation (11 providers)pomera_json_xml- Validate/prettify/convert configspomera_extract- Extract emails/URLs/patterns from textpomera_html- HTML content extraction (text/links/tables/forms)
- Python 3.11+ (Python 3.8+ supported but 3.11+ recommended)
- pip package manager
macOS:
# Tkinter support (for GUI, optional for MCP-only usage)
brew install python-tk@3.14 # Replace with your Python versionLinux (Ubuntu/Debian):
sudo apt-get install python3-tk # Optional, GUI onlyWindows: Tkinter included with Python from python.org
Step 1: Install Pomera
pip install pomera-ai-commanderStep 2: Verify installation
python -m pomera --versionStep 3: Add to MCP settings (see configuration section below)
Step 1: Install via npm
npm install -g pomera-ai-commanderStep 2: Or use npx (no install needed)
npx pomera-ai-commanderStep 3: Add to MCP settings (see configuration section below)
Step 1: Clone repository
git clone https://github.com/matbanik/Pomera-AI-Commander.git
cd Pomera-AI-CommanderStep 2: Install in development mode
pip install -e .Step 3: Add to MCP settings (see configuration section below)
Add Pomera to your MCP client's configuration file. The configuration varies by client:
Location: VS Code Settings → Cline → MCP Servers
Configuration:
{
"mcpServers": {
"pomera": {
"command": "python",
"args": ["-m", "pomera.mcp_server"],
"timeout": 3600,
"env": {}
}
}
}Location (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
Location (Windows): %APPDATA%\Claude\claude_desktop_config.json
Configuration:
{
"mcpServers": {
"pomera": {
"command": "python",
"args": ["-m", "pomera.mcp_server"],
"timeout": 3600
}
}
}Location: Cursor Settings → Features → Model Context Protocol
Configuration:
{
"mcpServers": {
"pomera": {
"command": "python",
"args": ["-m", "pomera.mcp_server"],
"timeout": 3600
}
}
}Location: Antigravity Settings → MCP → Manage MCP Servers
Configuration:
{
"mcpServers": {
"pomera": {
"command": "python",
"args": ["-m", "pomera.mcp_server"],
"timeout": 3600
}
}
}⏱️ Timeout: The
"timeout": 3600setting (in seconds) prevents MCP request timeouts during long-running AI operations. Cline, Cursor, and Claude Desktop all default to 60 seconds, which is too short forresearchanddeepreasoningcalls (60-300s). See Cline #1306.
If installed via npm, you can use npx instead:
{
"mcpServers": {
"pomera": {
"command": "npx",
"args": ["-y", "pomera-ai-commander"],
"timeout": 3600
}
}
}For development from source:
{
"mcpServers": {
"pomera": {
"command": "python",
"args": ["-m", "pomera.mcp_server"],
"cwd": "/absolute/path/to/Pomera-AI-Commander",
"timeout": 3600
}
}
}1. pomera_notes
- Operations: save, get, search, list, update, delete
- Value: Persistent memory — cross-session state, prevents re-pasting
- Token Savings: ~100K+ tokens/project
2. pomera_web_search
- Engines: Tavily (AI-optimized), Exa (neural), Brave, Google, DuckDuckGo, SerpAPI, Serper
- Value: Real-time information access — 7 engines with fallback
- Token Savings: ~50K tokens/search
3. pomera_read_url
- Function: Fetch URL content, convert HTML to clean markdown
- Value: Content extraction without browser overhead
- Token Savings: ~20K tokens/article
4. pomera_find_replace_diff
- Operations: validate, preview, execute (regex with auto-backup)
- Value: Safe regex with diff preview — prevents destructive iteration
- Token Savings: ~10K tokens/task
5. pomera_smart_diff_2way
- Formats: JSON, JSON5/JSONC, YAML, ENV, TOML (auto-detect)
- Value: Semantic config comparison — ignores formatting, detects real changes
- Token Savings: ~40K tokens/comparison (agents can't diff structured data in-context)
6. pomera_smart_diff_3way
- Strategies: report (list conflicts), keep_yours, keep_theirs
- Value: 3-way merge — auto-resolves non-conflicting changes, reports conflicts
- Token Savings: ~40K tokens/merge (impossible for agents to merge configs natively)
7. pomera_ai_tools
- Providers: OpenAI, Anthropic, Google AI, Groq, OpenRouter, Azure, + 5 more
- Actions: generate, research (web + reasoning), deep reasoning (6-step protocol)
- Value: Multi-model delegation — call specialized models for subtasks
8. pomera_json_xml
- Operations: validate, prettify, minify, convert (JSON ↔ XML)
- Value: Config validation before processing
- Token Savings: ~10K tokens/validation
9. pomera_extract
- Types: regex patterns, emails, URLs (with dedup/sort)
- Value: Data extraction from large documents
- Token Savings: ~30K tokens/extraction
10. pomera_html
- Operations: visible_text, clean_html, extract_links, extract_images, extract_tables, extract_forms
- Value: Structured HTML processing — companion to
read_url - Token Savings: ~15K tokens/page
11. pomera_generators - Password, UUID, lorem ipsum, random email, slug generation
12. pomera_text_stats - Word/char count, reading time, top words analysis
13. pomera_markdown - Strip, extract links/headers, table conversion
14. pomera_line_tools - Dedup, remove empty, add/remove numbers, reverse, shuffle
15. pomera_list_comparator - Compare lists, find unique/common/missing items
16. pomera_whitespace - Tabs/spaces conversion, line ending normalization
17. pomera_column_tools - CSV/TSV data processing
18. pomera_diagnose - MCP server self-diagnostics and health checks
19-26: pomera_case_transform, pomera_encode (base64/hash), pomera_string_escape, pomera_sort, pomera_translator, pomera_cron, pomera_timestamp, pomera_url_parser, pomera_email_header_analyzer, pomera_word_frequency
After adding Pomera to your MCP configuration:
Step 1: Restart your MCP client
Step 2: Verify Pomera is loaded
- Cline: Check MCP Servers list
- Claude Desktop: Look for Pomera tools in available tools
- Cursor: Check MCP status in settings
- Antigravity: Refresh MCP Servers list
Step 3: Test with a simple tool call
Example test:
Use pomera_generators to create a UUID
Expected response: A valid UUID v4 string
Step 4: Test Notes system (session persistence)
Use pomera_notes to save a test note with title "Test/Session/Memory"
Then in a new conversation:
Use pomera_notes to search for "Test*"
Expected: Previous note should be retrieved
1. pomera_web_search "topic" → Tavily/Exa for best results
2. pomera_read_url <best result> → clean markdown
3. pomera_html extract_links → gather all sources
4. pomera_notes save --title "Research/Topic/Findings"
5. Later: pomera_notes search "Topic*" → instant retrieval
1. pomera_json_xml validate → check original for errors
2. Edit config file
3. pomera_smart_diff_2way → semantic diff before vs after
4. pomera_json_xml validate → verify changes are valid
1. pomera_smart_diff_3way base=<original> yours=<your changes> theirs=<their changes>
2. Review auto-merged fields + conflicts
3. Re-run with conflict_strategy="keep_yours" or "keep_theirs"
4. pomera_notes save → audit trail
1. pomera_find_replace_diff --operation validate
2. pomera_find_replace_diff --operation preview → see diff
3. pomera_find_replace_diff --operation execute → apply with backup
1. pomera_ai_tools --action research --provider OpenAI → deep research with web search
2. pomera_ai_tools --action deepreasoning --provider "Anthropic AI" → structured analysis
3. pomera_notes save → persist findings
- Verify Pomera is installed:
python -m pomera --version - Check MCP config syntax (valid JSON)
- Restart MCP client after config changes
- Verify Python 3.11+ is installed:
python --version - Use full path to python executable in MCP config
- Windows: Try
python3orpyinstead ofpython
- Reinstall:
pip install --force-reinstall pomera-ai-commander - Check dependencies:
pip show pomera-ai-commander
- Check logs in MCP client
- Verify no port conflicts
- Try running directly:
python -m pomera.mcp_server(should show MCP server starting)
- Enable all 10 critical tools + smart diff tools for config verification
- Use Notes system to complement task_boundary workflow
- Leverage web_search + ai_tools for research during PLANNING mode
- Use
pomera_smart_diff_2wayto verify config changes after edits
- Notes system complements Memory Bank with FTS5 search
- Use
pomera_web_searchinstead of external MCP servers - Default to
pomera_find_replace_difffor regex operations - Use
pomera_smart_diff_3wayto resolve config merge conflicts
- Pomera fills massive gap (Cursor has NO text utility tools)
- Enable ALL tools (10 critical + 5 high-value + specialists)
- Use Notes for cross-session state, smart diff for config verification
- Sub-agents can delegate text processing to Pomera
- Use
pomera_ai_toolsfor multi-model delegation from sub-agents - Use
pomera_smart_diff_2wayto validate config changes - Notes store sub-agent findings and merge audit trails
Research shows:
- 78.5% token reduction with MCP code execution patterns (Anthropic)
- 70-80% aggregate savings for Pomera tool-heavy workflows
- 97% reduction for research workflows (150K → 4K tokens)
- 80% reduction for regex operations (10K → 2K tokens)
Why this matters:
- Lower API costs
- Faster response times
- Stay within context limits
- Reduced iteration cycles
Pomera works 100% offline by default. Optional API keys enable:
- Web Search: Brave Search API, Google Custom Search, Context7 (configure in Pomera GUI)
- Storage: Encrypted in local database (not in JSON config)
- Privacy: Keys never leave your machine
To configure (optional):
- Launch Pomera GUI:
python pomera.py - Go to Settings → API Keys
- Add keys for web search engines
- Keys are encrypted and stored locally
- Documentation: https://github.com/matbanik/Pomera-AI-Commander/tree/master/docs
- Tool Reference: Tools Documentation
- MCP Guide: MCP_SERVER_GUIDE.md
- Agentic AI Analysis: Why AI needs Pomera
- Troubleshooting: TROUBLESHOOTING.md
Quick Start: Install with pip install pomera-ai-commander, add to MCP config, restart client, test with pomera_generators or pomera_notes.
Installation guide for AI assistants | Last updated: February 2026