coverage — SaaS Think Tank Evidence MCP Resource
coverage
is one of 1 resource on the
SaaS Think Tank Evidence
MCP server. Connect the server and your client can attach it as context.
by client
How to attach coverage from your client
- Claude Code SaaS Think Tank Evidence Resource/coverage run in your project directory
- Claude Desktop SaaS Think Tank Evidence Resource/coverage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SaaS Think Tank Evidence Resource/coverage ~/.cursor/mcp.json
- VS Code SaaS Think Tank Evidence Resource/coverage .vscode/mcp.json
- Zed SaaS Think Tank Evidence Resource/coverage ~/.config/zed/settings.json
- Windsurf SaaS Think Tank Evidence Resource/coverage ~/.codeium/windsurf/mcp_config.json
- Cline SaaS Think Tank Evidence Resource/coverage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SaaS Think Tank Evidence Resource/coverage ~/.gemini/settings.json
- Grok SaaS Think Tank Evidence Resource/coverage .mcp.json (in your project root)
- ChatGPT SaaS Think Tank Evidence Resource/coverage Settings → Connectors → Advanced → Developer mode
- Claude.ai SaaS Think Tank Evidence Resource/coverage Settings → Connectors → Add custom connector
- LangChain SaaS Think Tank Evidence Resource/coverage pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 17 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.