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