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