Skip to main content
Glama
README.md
<div align="center">
    <img src="https://raw.githubusercontent.com/SmartFactory-KL/aas-mcp/main/docs/images/logo-aas-mcp-purple-500.png" alt="aas-mcp">
</div>

<div align="center">
  <a href="https://pypi.org/project/aas-mcp"><img src="https://img.shields.io/pypi/v/aas-mcp?color=%2334D058" alt="PyPI - Version"></a>
  <a href="https://github.com/astral-sh/ruff"><img src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json" alt="Ruff"></a>
</div>

**aas-mcp** is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that provides AI assistants with tools to interact with [Asset Administration Shells (AAS)](https://industrialdigitaltwin.org/en/content-hub/aasspecifications) via the [Eclipse BaSyx](https://www.eclipse.org/basyx/) REST API.

This MCP server enables AI assistants to perform full CRUD operations on AAS Shells, Submodels, and Submodel Elements, making it ideal for industrial automation, digital twin management, and AAS-based workflows.

### Features

- 🤖 **MCP Server** with 25+ tools for comprehensive AAS management
- 🔧 **Full CRUD Operations** on Shells, Submodels, and Submodel Elements
- âš™ī¸ **Health Monitoring** tools for AAS environment status
- 🔁 **Seamless Integration** with [Eclipse BaSyx](https://www.eclipse.org/basyx/) Environment REST API
- 📡 **AI-Ready** tools designed for intelligent automation workflows  

## 🚀 Installation

```bash
pip install aas-mcp
```

**Requires**: Python 3.10+

## 🚀 Usage

### Running the MCP Server

```bash
# Start the MCP server
aas-mcp
```

### Available Tools

The MCP server provides 25+ tools for AAS management:

#### Shell Management
- `get_shells` - Retrieve all AAS Shells
- `get_shell` - Get a specific Shell by ID
- `create_shell` - Create a new Shell
- `update_shell` - Update an existing Shell
- `delete_shell` - Delete a Shell

#### Submodel Management
- `get_submodels` - Retrieve all Submodels
- `get_submodel` - Get a specific Submodel by ID
- `create_submodel` - Create a new Submodel
- `update_submodel` - Update an existing Submodel
- `delete_submodel` - Delete a Submodel
- `get_submodel_value` - Get Submodel raw value
- `update_submodel_value` - Update Submodel value
- `get_submodel_metadata` - Get Submodel metadata

#### Submodel Element Management
- `get_submodel_elements` - Get all elements from a Submodel
- `get_submodel_element` - Get a specific element by path
- `create_submodel_element` - Create a new element
- `update_submodel_element` - Update an existing element
- `delete_submodel_element` - Delete an element
- `get_submodel_element_value` - Get element raw value
- `update_submodel_element_value` - Update element value

#### Reference Management
- `get_submodel_refs` - Get Submodel references from a Shell
- `create_submodel_ref` - Create a Submodel reference
- `delete_submodel_ref` - Delete a Submodel reference

#### Health & Monitoring
- `get_health_status` - Check AAS environment health
- `is_healthy` - Boolean health check

## 🔧 Configuration

### MCP Client Configuration

To use this server with MCP clients like [Claude Desktop](https://claude.ai/download), add it to your client's configuration:

```json
{
  "mcpServers": {
    "aas-mcp": {
      "command": "aas-mcp",
      "env": {
        "SHELLSMITH_BASYX_ENV_HOST": "http://localhost:8081"
      }
    }
  }
}
```

> â„šī¸ Change the value of `SHELLSMITH_BASYX_ENV_HOST` to match your BaSyx Environment host URL

The configuration format is similar for other MCP clients like LM Studio.

### BaSyx Environment Configuration

The MCP server connects to an Eclipse BaSyx environment. The default host is:

```
http://localhost:8081
```

You can override it in several ways:

- Set the environment variable:  
  ```bash
  export SHELLSMITH_BASYX_ENV_HOST=https://your-host:1234
  ```

- Create a `.env` file in your working directory with:  
  ```dotenv
  SHELLSMITH_BASYX_ENV_HOST=https://your-host:1234
  ```

Each tool also accepts a `host` parameter to override the default configuration dynamically.

## 🤝 Contributing

We welcome contributions! Please see our contributing guidelines for setup, testing, and coding standards.

TDQS

B3.4/5.0

Scored across 25 tools

Disambiguation3/5

Most tools are clearly distinct, but update_submodel_element can also create elements, overlapping with create_submodel_element. Additionally, get_health_status and is_healthy serve similar purposes, which could cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern, with plural forms for list operations (e.g., get_shells, get_submodels) and singular forms for specific items. The naming is predictable and uniform across the entire set.

Tool Count3/5

With 25 tools, the server sits at the high end of the acceptable range. The domain is broad, but the count feels heavy, especially with multiple variants for value, metadata, and elements.

Completeness4/5

The tool set covers CRUD for all main resources: shells, submodels, submodel elements, and submodel references. Minor gaps exist, such as lacking an update operation for submodel references and metadata access for elements, but core workflows are well supported.

Maintenance

ActivityInactive
ResponsivenessNo issues