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