Tools overview

The MCP server exposes a set of design-time tools that mirror the operations available in the Cockpit. Each tool operates on a specific artifact type. After a client is connected and authorized, an AI assistant can invoke these tools in response to natural-language instructions.

Every tool call runs as the signed-in user and passes through the same validation pipeline, edit-lock checks, and save hooks as the Cockpit. An MCP client cannot bypass platform-level constraints.

Artifact types and required roles

Each group of tools requires a specific access control role on the user account. If the role is absent, the tool fails immediately with an access denied error before any action is performed. Development package permissions apply on top of role checks for non-administrative users.

Artifact type Required role Read / write Reference page

APIs

apidesigner

Read and write

APIs

Applications

appdesigner

Read and write

Applications

Adaptive entities

adaptivedesigner

Read and write

Adaptive entities

Development packages

package

Read and write

Development packages

npm packages

npmmodules

Read and write

npm packages

Server scripts

scripteditor

Read and write

Server scripts

System logs

syslog

Read only

System logs

Tables

tabledefinition

Read and write

Tables

Web apps

webapp

Read and write

Web apps

What you can do with MCP

The following table maps common development tasks to the relevant tool page. Use it as a starting point when you are unsure which tools apply to your goal.

I want to…​ Go to…​

Write or edit a server-side JavaScript or TypeScript script

Server scripts

Organize server scripts into a project

Server scripts

Execute a server script and inspect its output

Server scripts

Create or update an application

Applications

Activate an application to make changes available at runtime

Applications

Build a React or Vue web app

Web apps

Create or modify a database table definition

Tables

Query rows from a database table

Tables

Define a custom data structure for the Adaptive Designer

Adaptive entities

Design or update an API registered on the platform

APIs

Add, install, or remove an npm package

npm packages

Group artifacts into a development package

Development packages

View or filter system log entries

System logs

Diagnose errors or trace script and request activity

System logs

Understand why a tool returned an access denied error

Access control

Tool call prerequisites

Before a tool call succeeds, the following conditions must be met:

  • The client holds a valid access token with the mcp:tools scope. See Authorization.

  • The user account has the role required by the tool group (see table above).

  • For non-administrative users, the target artifact belongs to a development package that the user’s roles grant access to. See Access control.

Related topics