Connect the platform to the way you already work.
Public guidance for platform concepts, connection paths, API boundaries and MCP. Customer credentials and deployment-specific details stay inside onboarding and customer-controlled configuration.
How to connect
Start with organization access and product context, then connect the engineering or security workflow that should provide data.
- Organization and access setup
- Product and release structure
- Integration scope
API
Authenticated APIs support integrations and automation while remaining inside tenant-scoped authorization boundaries.
- Product lifecycle context
- Evidence and workflow integration
- Service access for automation
Open MCP
Local-first CRA analysis for an MCP-compatible AI client. No embedded LLM and no AA-sec SaaS account required.
Compare MCP optionsPlatform MCP
Connect an authorized AI client to AA-sec product-security context without replacing the customer’s model choice or platform authorization.
Platform MCP overviewSecurity & decision boundaries
AA-sec structures product-security evidence and workflows. It does not certify CRA compliance or replace legal and organizational decision-making.
For AI
A direct Markdown resource gives tools and AI systems a concise machine-readable summary of AA-sec capabilities and boundaries.
Open For AI