Wfirma MCP server
io.github.agente-dev/wfirma-mcp·v1.0.0·1 starsUnofficial read-only MCP server for the wFirma API v2: invoices, contractors, expenses, payments.
1 stars38 downloads/wk
Reviews
Write oneNobody has reviewed Wfirma yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Wfirma tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
wfirma_list_companiesDiscover the client companies available to this wFirma accounting-office account. Returns internal company ids and NIPs separately.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 65 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
How Wfirma compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 38% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 38
- more than 29% of 12,191 servers with a package
What its tools let an agent do: 1 read
Install Wfirma in Claude Code, Cursor or VS Code
Runs npx -y wfirma-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add wfirma-mcp -- npx -y wfirma-mcp
What the publisher says
From the Wfirma repository's README, as published. We do not edit it. Read it on GitHub
wFirma MCP
Unofficial, read-only MCP server for the wFirma API v2 (api2.wfirma.pl). Gives MCP-compatible AI assistants typed, read-only access to company data, invoices, contractors, expenses, and payments — with credentials that never leave your machine and no commercial middleware between you and wFirma.
Not affiliated with wFirma. "wFirma" is a trademark of its respective owner.
Tools (9, all read-only)
Every company-scoped tool requires the internal companyId returned by wfirmalistcompanies. A Polish NIP is not accepted as a company id.
Why read-only
The server intentionally contains no add, edit, delete, send, fiscalization, KSeF, or payment-mutation operation. The full list of excluded categories, reviewed against the official documentation at doc.wfirma.pl, is recorded in coverage-manifest.json. If you need writes, use wFirma's own tooling — not this server.
Setup
Credentials
wFirma API keys are created in your wFirma panel (Integrations → API). Required environment variables:
- WFIRMAACCESSKEY
- WFIRMASECRETKEY
- WFIRMAAPPKEY
See .env.example. Never commit real values.
Build
pnpm install
pnpm build # → dist/index.js (self-contained esbuild bundle)
pnpm test # all HTTP traffic is mocked; no live account neededClaude Desktop / any stdio MCP client
{
"mcpServers": {
"wfirma": {
"command": "node",
"args": ["/absolute/path/to/wfirma-mcp/dist/index.js"],
"env": {
"WFIRMA_ACCESS_KEY": "your-access-key",
"WFIRMA_SECRET_KEY": "your-secret-key",
"WFIRMA_APP_KEY": "your-app-key"
}
}
}
}Claude Code / Cursor (scope: project)
claude mcp add wfirma -- node /absolute/path/to/wfirma-mcp/dist/index.jsDesign notes
Node's stdlib https with a hard 20s timeout and a bounded response-size guard.
- No runtime dependencies beyond the MCP SDK and zod. The client uses
ids, oversized responses, and auth failures each raise a distinct wfirma_* error code instead of a generic failure.
- Fail-closed error taxonomy. Missing credentials, non-numeric company
endpoint, risk class, and the test that proves it; a CI test enforces the manifest stays in sync with the source.
- No PII in logs. Tool parameters are never logged.
- Coverage manifest. coverage-manifest.json maps every tool to its
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Wfirma: common questions
- Is Wfirma MCP server safe?
- Mostly: it is graded B (72/100). Read the Wfirma safety report
- How do I install Wfirma?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Wfirma need an API key?
- Yes. The registry entry asks for
WFIRMA_ACCESS_KEY,WFIRMA_SECRET_KEY,WFIRMA_APP_KEY. - Is Wfirma maintained?
- The last commit was 69 days ago (2026-08-27). The latest release is v1.0.0.
- How does Wfirma compare with other MCP servers?
- safety score 72/100 (higher than 38% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.