find_niche — TGGET Niche Research MCP Prompt
find_niche
is one of 1 prompt on the
TGGET Niche Research
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find_niche from your client
- Claude Code TGGET Niche Research Prompt/find_niche run in your project directory
- Claude Desktop TGGET Niche Research Prompt/find_niche ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TGGET Niche Research Prompt/find_niche ~/.cursor/mcp.json
- VS Code TGGET Niche Research Prompt/find_niche .vscode/mcp.json
- Zed TGGET Niche Research Prompt/find_niche ~/.config/zed/settings.json
- Windsurf TGGET Niche Research Prompt/find_niche ~/.codeium/windsurf/mcp_config.json
- Cline TGGET Niche Research Prompt/find_niche ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TGGET Niche Research Prompt/find_niche ~/.gemini/settings.json
- Grok TGGET Niche Research Prompt/find_niche .mcp.json (in your project root)
- ChatGPT TGGET Niche Research Prompt/find_niche Settings → Connectors → Advanced → Developer mode
- Claude.ai TGGET Niche Research Prompt/find_niche Settings → Connectors → Add custom connector
- LangChain TGGET Niche Research Prompt/find_niche pip install langchain-mcp-adapters
TGGET Niche Research also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 6 October 2026.
A listing does not declare its prompts, 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 prompt's arguments.