MCP servers: what each one lets your AI agent do

Open the server’s detail page and the provider’s current setup guide for your client. Connection examples are included where recorded; they are starting points to check against the current server and client versions, not a promise that every listing has a configuration for every client. A local server may require a package, runtime and client configuration. A hosted server may connect through a URL and an authentication flow instead. Confirm the transport, required credentials and enabled tools, then try a bounded task before relying on the connection.

stdio is the default for local servers. The client spawns the server as a subprocess and talks over standard input/output. Fast, simple, and the server runs on your machine. SSE (Server-Sent Events) and Streamable HTTP are network transports. The server runs anywhere reachable over HTTPS and streams responses back. Use these for team-shared servers, cloud connectors, or anything you prefer to keep off your local machine.

Scores are existing editorial assessments recorded for individual servers. The accompanying notes may discuss tool coverage, setup, documentation, permissions and security considerations; the available detail and review dates vary by record. The practical workflow reviews for Firecrawl, GitHub and Exa are separately dated documentation reviews. They do not assign new ratings or establish that installation and tool execution have been tested. Compatibility labels, directory listings and hands-on checks are separate signals.

Directory inclusion, an editorial score or an official provider label is not a security certification. Check the source, maintenance, requested permissions and provider guidance. A locally run process may inherit your user permissions; remote services have their own access and data-handling considerations. Use credentials limited to the task, review the enabled tools and try an authorised test environment first. Recorded security notes can help identify questions to investigate. A documentation review does not establish that a server has passed installation testing or a security assessment.

Support depends on the client version, server transport and deployment. The directory’s compatibility labels describe recorded support; they do not by themselves show that a particular client and server combination has been installed and tested. Check the current setup instructions from the client and server providers. Where a record names a testing scope or date, read those details separately from its compatibility labels before choosing your configuration.

Open a PR against our public server index, or reach out via the submit form on the contact page. We accept editorial submissions only. Every listing is editorially chosen.

Our parent company Scaletific does, specifically for internal APIs, proprietary systems, and infrastructure that falls outside commodity SaaS. AutomationSwitch itself is the editorial and directory side. If the directory covers your use case, install and go. If you need something custom, the Scaletific CTA below is where to start.