The MCP server can now explain how Alunta works

AI Access (MCP) could already answer questions about your own numbers. Now the MCP server can also look things up in Alunta's product guides, the public API documentation and the release notes.

All product updates

Changed since - September 21, 2026
Test accounts can now be selected as a separate connection during authorization, with a clear indication that the account is a test account. This was not available at the August product-knowledge introduction. See the AI Access and data security guide (Markdown file, AI agent-friendly) for current choices.

AI Access (MCP) could already answer questions about your own numbers. Now the MCP server can also look things up in Alunta’s product guides, the public API documentation and the release notes.

That means you can ask things like “why was no invoice created for this customer”, “when is the customer’s card charged”, “what does the status under_cancellation mean” or “what is new since I last logged in”, and get an answer based on how Alunta actually behaves.

The guides describe Alunta in general. Whether a feature is enabled for your team is in your own settings, and the MCP server checks that separately.

You do not need to do anything to get access. If you have already connected AI Access, the new tool is there the next time you ask, although some AI clients need to refresh their tool list first.

Access is still read-only, and nothing has changed about what your AI can see of your data.

Historical background - August to September 2026

Product knowledge and current team metrics are two different answer paths. You can ask “What does Pending MRR mean?” for a general explanation and then ask about your own subscriptions or usage data when the administrator has approved the relevant categories. Check the team carefully during authorization.

AI Access is read-only. If a field is missing, check the data category and the team’s current app status; a field existing in Alunta does not automatically mean that AI may see it. See the AI Access and data security guide (Markdown file, AI agent-friendly) for current choices and revocation.

Bo Møller
Bo Møller
Emil Højbjerg
Emil Højbjerg

The people and AI helpers behind the updates

Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.

The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.