search_similar_projects — One's Vibe MCP Tool Read-only
search_similar_projects
(search similar projects) is one of 1 tool on the
One's Vibe
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_similar_projects from your client
- Claude Code One's Vibe search_similar_projects run in your project directory
- Claude Desktop One's Vibe search_similar_projects ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor One's Vibe search_similar_projects ~/.cursor/mcp.json
- VS Code One's Vibe search_similar_projects .vscode/mcp.json
- Zed One's Vibe search_similar_projects ~/.config/zed/settings.json
- Windsurf One's Vibe search_similar_projects ~/.codeium/windsurf/mcp_config.json
- Cline One's Vibe search_similar_projects ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI One's Vibe search_similar_projects ~/.gemini/settings.json
- Grok One's Vibe search_similar_projects .mcp.json (in your project root)
- ChatGPT One's Vibe search_similar_projects Settings → Connectors → Advanced → Developer mode
- Claude.ai One's Vibe search_similar_projects Settings → Connectors → Add custom connector
- LangChain One's Vibe search_similar_projects pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http search https://onesvibe.app/api/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.