find_topic_content — TCC Group website MCP Prompt
find_topic_content
is one of 2 prompts on the
TCC Group website
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find_topic_content from your client
- Claude Code TCC Group website Prompt/find_topic_content run in your project directory
- Claude Desktop TCC Group website Prompt/find_topic_content ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TCC Group website Prompt/find_topic_content ~/.cursor/mcp.json
- VS Code TCC Group website Prompt/find_topic_content .vscode/mcp.json
- Zed TCC Group website Prompt/find_topic_content ~/.config/zed/settings.json
- Windsurf TCC Group website Prompt/find_topic_content ~/.codeium/windsurf/mcp_config.json
- Cline TCC Group website Prompt/find_topic_content ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TCC Group website Prompt/find_topic_content ~/.gemini/settings.json
- Grok TCC Group website Prompt/find_topic_content .mcp.json (in your project root)
- ChatGPT TCC Group website Prompt/find_topic_content Settings → Connectors → Advanced → Developer mode
- Claude.ai TCC Group website Prompt/find_topic_content Settings → Connectors → Add custom connector
- LangChain TCC Group website Prompt/find_topic_content pip install langchain-mcp-adapters
Other prompts on this server
TCC Group website also offers 4 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 11 November 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.