Sonar MCP
Use Sonar’s profile-specific Model Context Protocol interface for tools and agent skills.
Sonar MCP is Sonar's Model Context Protocol interface. It exposes a profile-specific set of Sonar tools and agent skills without turning MCP into an Astrixion-wide product or a second domain model.
Responsibility
Sonar MCP:
- translates MCP tool calls into authenticated Sonar API calls;
- filters tools and prompts through a fail-closed profile;
- offers Inventory reads, workflow and scan reads, bounded recon execution, structural authoring, approved asset synchronization, or administration according to that profile;
- serves selected Sonar agent skills as MCP prompts.
The Sonar API remains authoritative. Hiding a tool from a profile reduces the exposed surface; it does not replace backend authorization.
Capability flow
Start with Inventory when using Sonar MCP. If the program ID is unknown, discover it with
list_programs; then call get_target_overview and page into the relevant asset types. Starting a
scan is a separate, consequential action.
Read this interface
Security and profiles
The tier, allow-list, service-identity, and backend-policy boundaries — and why hiding a tool is not the same as removing authorization.
Connect
Remote Streamable HTTP, local stdio, and the operator configuration each transport needs.
Tool reference
Tools grouped by Sonar capability, with the safe first-use sequence.
For task-level procedures, use Sonar guides or load one of the profile's MCP prompts. Canonical meanings remain in the Inventory and workflow-engine subsystems.