Biurko
io.biurkoPublished by biurko.ioOfficial publisherv0.86.0Updated Oct 24, 2026
Polish invoicing and KSeF e-invoicing: issue, send, settle and file a company's documents
Overview
A remote MCP endpoint for Polish invoicing and KSeF e-invoicing that lets an assistant issue, send, settle and file a company's documents.
- What you can do
- Issue invoices and other company documents through the service's Polish invoicing workflow, including KSeF e-invoicing handling as described in the registry listing. Send issued documents to their recipients. Record settlement of documents. File and organize a company's documents. The manifest lists no individual tools, so the exact operations available to an assistant are not specified here.
- When to use it
- Relevant for Polish companies or their accountants who already work with the Biurko service and want an assistant to handle invoicing and KSeF e-invoicing tasks alongside their normal workflow.
- Requirements
- A remote streamable HTTP endpoint at app.biurko.io; no packages, environment variables or headers are declared. The manifest declares no authentication, but the service is an account-based invoicing platform, so expect to need a Biurko account and whatever sign-in the service requires.
Installation
In SourceWeft
- Open Biurko in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.biurko%2Fbiurko/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"biurko": {
"type": "http",
"url": "https://app.biurko.io/mcp"
}
}
}Tools
0Version history
1- v0.86.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.