Claude Code MCP Servers

Choose by task and evidence

Choose a Claude Code MCP connection around the resource you need to reach. The reviewed candidates include library documentation, GitHub repositories and browser inspection, each with a different permission boundary. A documentation lookup does not need repository write access, and a browser debug session should not share an ordinary signed-in profile by default. Follow the client setup linked from the selected source, then match the declared transport and authentication requirements. The agent tag comes from repository setup documentation, not a test of every available tool. Begin with one read-only request, check which account or browser instance answered and inspect the result before expanding access. A Claude plugin may already configure the same MCP service, so compare the plugin components before adding another connection. Keep package runtime requirements, account costs and tool permissions as separate decisions.

Agent labels reflect detected manifests or repository setup documentation. The runtime of each entry has not been tested in every client. Use the evidence links to check your exact client and version.