Skip to content

MCP or REST? ​

MCP and skillsREST API
CountriesFinland now; Sweden Q3 2027; Denmark and Norway plannedFinland only
Who calls itAn agent, on behalf of a user in conversationYour code
Domain knowledgeShipped with it, in the skillsYours to build from the docs
Coverage todayPayroll and reports; not every area yet (status per area)Complete
Best forChat and voice experiences, AI assistants, new integrations, multi-country productsDeep integrations with your own UI and workflows

Choose MCP when ​

  • you are building a conversational or agentic experience — your own chat, an assistant in your product, or a user's Claude Desktop;
  • your users are not payroll professionals and need the agent to explain, ask the right business question and refuse what should not be done;
  • you want to be ready for Sweden and the other Nordic countries — they will not be available on the REST API.

Choose REST when ​

  • you need the full Finnish feature set today;
  • your integration is not agentic — batch imports, your own UI, back-office automation;
  • you are an existing partner already on the API.

Both ​

They are not exclusive. A natural pattern is: your software uses the REST API for account setup and payment, and an agent in the same product uses MCP to answer payroll questions and prepare calculations.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.