M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionUnstructured API MCP ServerManage Unstructured API sources, destinations, and workflows via MCPMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS36 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions7 / 2018 / 20
Maintenance3 / 2016 / 20
Documentation11 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • Users who need to manage Unstructured workflows and connectors programmatically through an MCP client
  • Teams that already have an Unstructured API key and know the platform concepts
  • Users who want to feed web crawl results into Unstructured workflows
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Production environments needing active maintenance and support (the server is not actively maintained)
  • Users who only need to parse and transform files into structured output (use the Unstructured Transform MCP server instead)
  • Users without an Unstructured API key or the required connector credentials
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires an Unstructured API key (UNSTRUCTURED_API_KEY)
  • Creating/updating/deleting connectors requires connector-specific credentials in the .env file, such as AWS_KEY, AWS_SECRET, WEAVIATE_CLOUD_API_KEY, PINECONE_API_KEY, ASTRA_DB_APPLICATION_TOKEN, AZURE_CONNECTION_STRING, NEO4J_PASSWORD, MONGO_DB_CONNECTION_STRING, GOOGLEDRIVE_SERVICE_ACCOUNT_KEY, DATABRICKS_CLIENT_ID/SECRET, OneDrive and SharePoint client credentials, SALESFORCE_CONSUMER_KEY and SALESFORCE_PRIVATE_KEY
  • Firecrawl features require FIRECRAWL_API_KEY
  • Adding terminal access to the minimal client (desktop-commander) gives the client and LLM access to private files
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • The server is not actively maintained and may contain unfixed issues
  • Delete tools remove connectors, workflows, or jobs and misuse can cause data loss
  • update_workflow does not apply a patch; it fully replaces the workflow config, so the existing config must be in context (e.g. via get_workflow_info) or it may be overwritten
  • Setting CONFIRM_TOOL_USE to false may let the LLM execute expensive workflows or delete data
  • Defining many third-party credentials in .env widens the impact of credential leakage
  • Adding terminal access to the minimal client allows the LLM to access private files
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools260