MCP server for governed enterprise analytics
An agent never opens your dashboard, so any control that lives only in the interface does not apply to it.
A question becomes a decision
Which accounts need a closer look?
- 01
Connect
Permitted analytical tools
- 02
Resolve meaning
Each tool request retains the user's scope
- 03
Review the answer
An analysis to review. Asking a question does not authorize a business-system change.
Illustrative workflow. Results depend on configured sources, definitions, and permissions.
Nexatron exposes a Model Context Protocol server over Streamable HTTP (JSON-RPC 2.0) secured with OAuth 2.1, so an MCP-capable client can ask governed questions of connected sources. Governance is enforced inside the same pipeline that serves the product's own interface, so an agent and a person asking the same question of the same source receive the same answer and both appear in the same audit log.
What it does
- The agent inherits a human's reachPer-user authorization means what the agent can read is bounded by what the person it acts for could read, rather than by what a shared integration account could read.
- One pipeline, two doorsThe MCP path runs the same row-level security, the same certified metrics and the same semantic layer as the product interface. There is no second, looser path that exists because it was easier to build.
- A tiered tool surfaceAnalytics tools are always on. The action-taking tools are a separate, entitlement-gated tier: on by default, and a workspace admin can switch it off, so read access and write capability are decisions you make separately.
- Audited answersGoverned answers in Ask are written to a tenant-keyed, hash-chained audit log.
What it deliberately won’t do
Each of these is a case where returning something would have been easy and wrong, so the product is built not to.
- It will decline to an agent as readily as to a personAgents explore, so they ask for things that are not there more often than people do. The refusal path is the same one, and it names the boundary rather than returning something adjacent.
- Cross-source rules hold for agents tooAn agent's cross-source question goes through the same checks as a person's. Where a workspace requires a certified link between two systems and none exists, the agent is told the link is absent.
Test the claim, don’t take it
Ask it something you already know the answer to, then ask it something your data cannot answer. Those two questions tell you more than a feature list.