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