
What it does
Connect your enterprise architecture data to your AI tools
MCP (Model Context Protocol) is an open standard for connecting AI tools to external systems and data. The Avolution ABACUS MCP Server gives users and AI agents across your organization direct, conversational access to your enterprise architecture data.
-
Works with your AI tools
Connect Claude, Copilot or any other MCP compatible tool to ABACUS.
-
NL
QueryingAsk in your own words. No ABACUS terminology, data model or query syntax needed.
-
Built on the AI Assistant
Understands your architecture data and translates it into clear answers, not raw results.
-
Secure
accessEvery session uses an ABACUS user account and respects its data permissions.
-
Read
onlyAnswers questions about your ABACUS data. It cannot create, update or delete anything.
Who it is for
Put enterprise architecture data in reach of the whole organization
Anyone who uses an AI tool day to day can use it, not just architects.
- Leaders can interrogate live data instead of waiting for a report to be prepared.
- Department heads can see how a proposed change affects their area without a technical briefing.
- Project teams can surface dependencies and risks faster.
- AI agents can draw on ABACUS data as part of automated workflows.
Your architecture data stops sitting with specialists and becomes something the whole organization can use.


What you can ask
Turn questions into actionable intelligence
The MCP Server supports the same use cases as the ABACUS AI Assistant. A few examples to start with.
- “Highlight the applications with the highest risk.”
- “Show me the downstream systems impacted if we retire our CRM application.”
- “What changes to my architecture would reduce costs?”
- “Summarize what I as a CTO should be concerned about within my architecture.”
How it works
How the ABACUS MCP Server works in three steps
Connect
Connect ABACUS to the AI tools your teams already use, such as Claude, Copilot or other MCP-compatible tools.
Step 1
Ask
Ask natural-language questions about your architecture data, just as you would in the built-in ABACUS AI Assistant.
Step 2
Get answers
Get the information relevant to your task, grounded in your data, without needing to know the underlying data model or query syntax.
Step 3
Data privacy
Your data stays yours
Every session is authenticated with an ABACUS user account and respects that account’s data permissions, so users and agents can only access data that account is permitted to see. Your data is not used to train AI models.
Frequently asked questions
What is the ABACUS MCP Server?
The ABACUS MCP Server connects MCPcompatible AI tools, such as Claude and Copilot, to your enterprise architecture data in ABACUS, so users can ask questions about it in plain language. It is built on the ABACUS AI Assistant and is read-only.
What is MCP?
MCP (Model Context Protocol) is an open standard for connecting AI tools and agents to external systems and data.
Which AI tools can I connect?
Any MCP-compatible AI tool, such as Claude or Copilot.
Do I need an ABACUS account?
Yes. Every session is authenticated with an ABACUS user account.
Does it respect our data permissions?
Yes. It respects the data permissions of the account used to authenticate, so users and agents can only access data that account is permitted to see.
Can it edit my data?
No. The MCP Server is read-only. It can answer questions about your ABACUS data, but it cannot create, update or delete anything.
Is my data used to train AI models?
No, your data is not used to train AI models.
Your architecture intelligence, wherever your teams already work.