← ClaudeAtlas

automation-pilot-mcp-server-generationlisted

Create, configure, and deploy SAP Automation Pilot MCP server definitions and tool configurations. Use when building MCP servers, defining tools, setting up Automation Pilot MCP configs, or deploying MCP server definitions via API.
williamcorrea23/sap-router-skill · ★ 1 · AI & Automation · score 66
Install: claude install-skill williamcorrea23/sap-router-skill
# SAP Automation Pilot MCP Server Definition Generator This skill guides the creation of MCP server definitions for SAP Automation Pilot. MCP server definitions are JSON files that expose Automation Pilot commands as MCP tools, allowing AI assistants to invoke them directly. --- ## JSON Schema ### Top-Level Structure Every MCP server definition follows this structure: ```json { "name": "kebab-case-server-name", "enabled": true, "instructions": "<Natural-language description for the AI>", "mcpTools": [ ...tool objects... ] } ``` | Field | Type | Description | |-------|------|-------------| | `name` | string | Kebab-case identifier (e.g., `cf-app-management`). Must match filename without `.json`. No spaces. | | `enabled` | boolean | Activates/deactivates the entire server | | `instructions` | string | Natural-language guidance for the AI on what this server does and when to use it | | `mcpTools` | array | Array of tool definitions (1 or more) | ### Tool Object Structure Each entry in `mcpTools` uses exactly this schema — all fields are required: ```json { "commandId": "<catalog>-<suffix>:<CommandName>:<version>", "name": "<snake_case_tool_name>", "enabled": true, "inputReferences": [ "<catalog>-<<<TENANT_ID>>>:<InputName>:<version>" ], "tags": {}, "title": "<Title Case Label>", "destructiveHint": false, "idempotentHint": false, "openWorldHint": true, "readOnlyHint": false } ``` | Field | Type | Description | |-------|------|---------