mcp
nullreport/mcp
Controle seu gerador de relatórios self-hosted via IA
Ver no GitHubLocal MCP server for NullReport: drive your self-hosted report generator from an AI client like Claude or Cursor.
Instalação
npx convez-ai nullreport/mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automatizar criação e edição de relatórios técnicos via conversa com Claude
- Integrar NullReport com workflows de IA em Cursor ou Claude Desktop
- Gerenciar achados e seções de relatórios sem sair do editor
Veredito

Integração bem estruturada que torna NullReport acessível via IA com segurança (token único, sem deletes). Exige instância NullReport própria, adequado para equipes técnicas que já usam a ferramenta e querem automação via Claude.
README
A tradução para o português deste README ainda está na fila.
nullreport-mcp
A local MCP server that lets an AI client (Claude Desktop, Cursor, Claude Code) drive your own self-hosted NullReport instance in natural language: browse and search reports and the finding library, create and edit findings and sections, and export to DOCX.
It runs on your own machine and talks only to your NullReport backend, authenticated with a token you generate. It is a thin wrapper over NullReport's REST API, so it inherits all of NullReport's rules: your role, your tier, and every validation are enforced exactly as in the web app. It deliberately has no delete tools; deleting data stays in the web UI.
Requirements
- A running NullReport instance (version with MCP support).
- Node.js 18+ on the machine running your AI client.
Setup
- In NullReport, open Settings → MCP Access and click Generate MCP token. Copy the config block it shows. The token is shown once.
- Paste it into your AI client's MCP config. For Claude Desktop that is
claude_desktop_config.json:
{
"mcpServers": {
"nullreport": {
"command": "npx",
"args": ["-y", "nullreport-mcp"],
"env": {
"NULLREPORT_URL": "http://localhost:3000",
"NULLREPORT_TOKEN": "<your token>",
"NULLREPORT_OUTPUT_DIR": "~/nullreport-exports"
}
}
}
}
- Restart your client. It will fetch and run
nullreport-mcpon demand.
Environment
| Variable | Required | Meaning |
|---|---|---|
NULLREPORT_URL | yes | The address you open NullReport at (a standard install is http://localhost:3000; the /api path is proxied to the backend from there). Use your custom domain if you have one. |
NULLREPORT_TOKEN | yes | The token from Settings → MCP Access. |
NULLREPORT_OUTPUT_DIR | no | Where exported DOCX files are written. Defaults to ~/nullreport-exports. |
Tools
Read, write, and export, no deletes:
whoamilist_reports,get_report,create_report,update_reportcreate_section,update_section,reorder_sectionscreate_finding,update_finding,reorder_findingssearch,list_finding_templates,get_finding_template,create_finding_from_templatelist_report_templates,export_report
export_report writes the DOCX to NULLREPORT_OUTPUT_DIR and returns the file path. list_reports returns a cursor-paginated object; the reports are under its data field.
Revoking access
Open Settings → MCP Access in NullReport and click Revoke. The current token stops working immediately. Generating a new token also invalidates the previous one, so there is only ever one active token per user.
Development
npm install
npm test
Support
Found a bug or want a feature? Open an issue at nullreport/feedback. For help, licensing, or anything private, email support@nullreport.app.
License
MIT. See LICENSE. NullReport itself is commercial software; this client is open so you can read exactly what it runs.