diagnostico_emissao — fiscal MCP Prompt

diagnostico_emissao is one of 5 prompts on the fiscal MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke diagnostico_emissao from your client

• Claude Code fiscal Prompt/diagnostico_emissao run in your project directory
• Claude Desktop fiscal Prompt/diagnostico_emissao ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor fiscal Prompt/diagnostico_emissao ~/.cursor/mcp.json
• VS Code fiscal Prompt/diagnostico_emissao .vscode/mcp.json
• Zed fiscal Prompt/diagnostico_emissao ~/.config/zed/settings.json
• Windsurf fiscal Prompt/diagnostico_emissao ~/.codeium/windsurf/mcp_config.json
• Cline fiscal Prompt/diagnostico_emissao ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI fiscal Prompt/diagnostico_emissao ~/.gemini/settings.json
• Grok fiscal Prompt/diagnostico_emissao .mcp.json (in your project root)
• ChatGPT fiscal Prompt/diagnostico_emissao Settings → Connectors → Advanced → Developer mode
• Claude.ai fiscal Prompt/diagnostico_emissao Settings → Connectors → Add custom connector
• LangChain fiscal Prompt/diagnostico_emissao pip install langchain-mcp-adapters

Other prompts on this server

• emitir_nfe_simples
• cancelar_nota
• relatorio_periodo
• carta_correcao

fiscal also offers 1 resource — 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.