coverage — NewHomeSearch MCP Resource
coverage
is one of 3 resources on the
NewHomeSearch
MCP server. Connect the server and your client can attach it as context.
by client
How to attach coverage from your client
- Claude Code NewHomeSearch Resource/coverage run in your project directory
- Claude Desktop NewHomeSearch Resource/coverage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NewHomeSearch Resource/coverage ~/.cursor/mcp.json
- VS Code NewHomeSearch Resource/coverage .vscode/mcp.json
- Zed NewHomeSearch Resource/coverage ~/.config/zed/settings.json
- Windsurf NewHomeSearch Resource/coverage ~/.codeium/windsurf/mcp_config.json
- Cline NewHomeSearch Resource/coverage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NewHomeSearch Resource/coverage ~/.gemini/settings.json
- Grok NewHomeSearch Resource/coverage .mcp.json (in your project root)
- ChatGPT NewHomeSearch Resource/coverage Settings → Connectors → Advanced → Developer mode
- Claude.ai NewHomeSearch Resource/coverage Settings → Connectors → Add custom connector
- LangChain NewHomeSearch Resource/coverage pip install langchain-mcp-adapters
Other resources on this server
NewHomeSearch also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 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.