Catalog vs Carbone MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Catalog vs Carbone MCP
In-depth architectural comparison of the Catalog and Carbone MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Catalog
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Carbone MCP
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Catalog if you need specialized Developer Tools tools running via a local process. Choose Carbone MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
C
Choose Catalog when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
All MFOs in the catalog with borrower rating and canonical card URLs. `rating: null` means *no reviews yet*, not a low score.
get_mfo
Full MFO card: terms for new and repeat clients (amount, term, rate), effective annual rate (ГЭСВ), requirements, fees, legal data (legal entity, BIN, ARDFM license number and a direct link to the company's record in the regulator's license register), 4-criteria rating, record update date.
search_offers
Matching first-loan offers with terms and `first_loan_zero_percent: true/false/null` (null = unconfirmed). Calling without filters returns the whole catalog — prefer passing `amount`/`term_days`.
list_categories
Catalog selections grouped by section (popular, by payout method, by amount and term, by borrower category), each with its selection criterion.
get_category
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Catalog is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Carbone MCP belongs to Developer Tools using local stdio subprocess. Select Catalog when you need capabilities focused on developer tools and Carbone MCP when you require tools for developer tools.
One selection: criterion, sorting, offer table with per-MFO terms.
get_reviews
Latest borrower reviews for an MFO: rating, date, text (public site data only).
get_market_rules
Legal context of microlending in Kazakhstan (ARDFM licensing, 46% APR cap, short microloans up to 45 MCI / 45 days at ≤0.3% per day, voluntary loan self-ban via eGov) with the last-review date.
Carbone MCP Tools (11)
convert_document
Convert documents between 100+ formats without storing a template
render_document
Generate documents from templates by merging with JSON data
list_templates
Browse your template library with filtering by category or search (tags are returned per template but not filterable server-side)
list_categories
List all template categories in your account
list_tags
List all tags used across your templates
upload_template
Store reusable templates with versioning, categorization, and metadata
update_template_metadata
Rename, categorize, tag, deploy, or expire template versions
delete_template
Soft-delete templates (marked for removal, gone after ~24h)
download_template
Download original template files (DOCX, XLSX, PDF, etc.)
get_api_status
Check Carbone API health and current version
get_capabilities
View all supported formats, features, and examples