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