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 MCPGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS36 / 100 · D76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions7 / 2014 / 20
Maintenance3 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience9 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools2615