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