A fixed asset register that depreciates on the rates the tax authorities actually publish, with the schedule, the journal and the gain on sale. You give it what you bought, what it cost, when it went into use and which category it falls in; it gives back the rate, the useful life, the convention, the full schedule year by year or month by month, one month's journal entry, and the gain or loss when you sell. Three tables ship with it: the Polish annual rates from the annex to the CIT and PIT acts keyed to the KST classification, 33 rows with the declining-balance eligibility of each and the art. 16k switch to straight line; the UK capital allowance pools at 18 and 6 percent with the annual investment allowance; and the US MACRS GDS half-year percentages for 3, 5 and 7 year property exactly as IRS Pub 946 Table A-1 publishes them. The convention belongs to the table rather than to the caller, so Poland charges from the month AFTER the asset enters the register and an asset in service on 15 March starts on 1 April with year one at nine twelfths, the MACRS percentages already carry the half-year convention, and a UK writing down allowance is a pool allowance that is not prorated by month at all. The same asset gives three different year-one figures under the three schemes and all three are right. Money is integer minor units end to end and the schedule is allocated by cumulative rounding, so the periods sum to cost less residual to the minor unit and the months sum to their own year. The tables are files inside the package rather than a feed, and every rate carries its authority, instrument, source URL and effective date.
In agent mode asset_schedule is a pure function of its arguments and touches no file, so an agent can depreciate the same purchase under all three schemes in one turn to see which figure it is actually filing. Only asset_add, asset_dispose and the license tools write, and only asset_add spends one of the ten free register slots.
| You say | Tool |
|---|---|
| I bought a Dell workstation for 8,499 zloty and put it into use on 15 March 2026. It is a computer. Add it to my fixed asset register and tell me what rate it depreciates at and what the schedule looks like. | asset_add |
| Show me that same asset month by month instead, and confirm the monthly amounts add back up to the yearly ones and to the depreciable base. | asset_schedule |
| We also bought a delivery truck for 10,000 zloty. Can I depreciate that one declining balance in Poland, and if so what are the first four years? | asset_schedule |
A depreciation rate the bundled table does not carry is refused by name rather than approximated to the neighbouring one. Measured through a real client on 2026-09-05, six prompts on the free tier, 16 of 18: asked for a US 10-year property class, the model called asset_schedule, got the server's own refusal (3, 5 and 7 year GDS half-year only; the 10, 15 and 20 year classes are not bundled), relayed it in those terms and said plainly it would not reconstruct Pub 946's 10-year percentages from memory. The 7-year row was not substituted, which is the exact defect the refusal exists to prevent. In the same session a Polish computer at 8,499.00 came back at the KST 487 annex rate of 30 percent with the first charge in April rather than the March it went into service, the four periods 1,912.28 / 2,549.70 / 2,549.70 / 1,487.32 summing to 8,499.00, and all 45 monthly rows reconciling to their own years and to the base. A 10,000.00 MACRS 5-year asset reproduced Pub 946 Table A-1 exactly across six periods. Every figure was re-derived over stdio afterwards and matched to the minor unit.
The file is .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the user profile mcp.json, opened by the MCP: Open User Configuration command |
// .vscode/mcp.json (the key is "servers")
{
"servers": {
"asset-register": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-asset-register"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"asset-register","command":"npx","args":["-y","@theluckystrike/mcp-asset-register"]}'VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.
The npm publish of @theluckystrike/mcp-asset-register is pending; until then use the .mcpb bundle or a clone and build from the latest release.
The same server runs at https://mcp.zovo.one/mcp/https://mcp.zovo.one/mcp/asset-register over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"servers": {
"asset-register": {
"url": "https://mcp.zovo.one/mcp/https://mcp.zovo.one/mcp/asset-register",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.
Free: Depreciation schedules are unlimited on every tier, on all three tables: the rates are public information a tax authority published, and metering the reading of a regulation would be charging for the government's work rather than for this server's. The cap is on the SIZE of the register, 10 assets, plus unlimited asset_list and asset_dispose. Pro is $19 once, verified offline.
The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.
No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.
In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.
MCP Asset Register in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro