Aas MCP Server
Asset Administration Shell APIs bridged for LLM agent interaction via MCP.
Data last scanned today · Reviewed today
Overview
Aas MCP Server functions as an OpenAPI-to-MCP adapter specifically designed for interacting with Asset Administration Shell (AAS) backends. By mapping AAS service specifications to MCP tools, it allows AI models to query and manage industrial assets directly through standard AAS-compliant interfaces like Eclipse BaSyx or FA³ST Service. Configuration is managed via YAML, which provides granular control over exposed endpoints. Users can perform fine-grained filtering by creating an intersection between official and implementation-specific specs, or by defining precise allowlists for HTTP methods and paths, including support for global wildcards.
Our verdict
This server carries a high risk level with a security score of 40/100. The primary concern is that it lacks an editorially reviewed authentication method and has not undergone verification for its read-only mode safety. Given that it is a community-maintained project rather than an official SAP release, users should exercise caution in production environments until these security criticalities are addressed.
- Zero direct dependencies reduce potential supply-chain vulnerabilities.
- Supports fine-grained access control through YAML allowlists.
- Active development with recent commits three days ago.
- Documentation includes specific setup steps for AAS integration.
- Security score of 40/100 indicates high risk level.
- Authentication methods have not been editorially reviewed.
- Not maintained by the official vendor.
- Read-only mode implementation has not been reviewed.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the primary system requirements for running the AAS MCP Server?
You need Python 3.12 or higher, AAS OpenAPI specifications, and an AAS-compliant backend server such as Eclipse BaSyx or FA³ST Service.
›How can I restrict which API endpoints the LLM can access?
You can use the curation section in your config.yaml file to define an allowlist, which supports specific path definitions and wildcards for HTTP methods and paths.
›Can I rename the tools exposed to the LLM?
Yes, you can use the aliases section in your configuration file to map specific API operations to custom tool names.
›Is it possible to filter endpoints based on my specific backend implementation?
Yes, you can provide both an official specification and an implementation-specific specification in your configuration to expose only the intersection of supported endpoints.
›Does the server support remote connections beyond local stdio?
Yes, the server supports HTTP transport with OAuth 2.1 for remote deployments, which can be configured using environment variables in a Docker container.
Changelog
- Securityv0.1.0
2026-07-29
Badge
Maintain this server? Add the live badge to your README.