Appaloft MCP server

The Appaloft MCP server is the callable tool entrypoint for Appaloft. It exposes the existing operation catalog to MCP clients without creating a separate AI-only product model. The skill owns workflow judgment; MCP executes precise command/query tool calls when configured.

Start the stdio server:

appaloft mcp stdio

Starting the server does not deploy apps, create resources, or mutate state. State changes only happen when an MCP client calls a concrete Appaloft operation tool.

@appaloft/ai-mcp is the repository source package that owns MCP transport code, descriptors, resources, prompts, and tests. A standalone appaloft-mcp package/bin is deferred until release packaging is wired; the current documented entrypoint is appaloft mcp stdio.

Each tool maps to one operation key:

• deployments.create -> deployments_create
• deployments.plan -> deployments_plan
• resources.configure-source -> resources_configure_source
• runtime-monitoring.samples.list -> runtime_monitoring_samples_list
• system.doctor -> system_doctor

Tool descriptors come from packages/application/src/operation-catalog.ts, and input JSON schemas come from the same command/query Zod schemas. Commands dispatch through CommandBus.execute, queries dispatch through QueryBus.execute, and calls use entrypoint: "mcp".

Tool descriptors include MCP annotations for read-only queries, destructive commands, idempotent queries, and operations that may touch external systems. Tool responses include JSON text and structured content, supporting both older clients and hosts that understand structured results.

There is no quick_deploy_create agent-only tool. If a behavior is not in the operation catalog, it is not an Appaloft MCP operation.

Read-only resources:

• appaloft://operation-catalog
• appaloft://tools/high-value
• appaloft://skill/appaloft
• appaloft://skill/deploy-protocol
• appaloft://tools/mcp-guide
• appaloft://docs/agent

Prompts:

• appaloft-first-deploy
• appaloft-recover-deployment
• appaloft-configure-resource
• appaloft-observe-runtime
• appaloft-publish-static-artifact

Resources and prompts provide context and workflow starters only. They do not own write-side policy, tenant selection, background work, or hidden state.

• Do not bypass Appaloft by calling repositories, use cases, provider SDKs, Docker, SSH, proxies, or databases directly.
• Do not read or output .env, private keys, tokens, cookies, database URLs, cloud credentials, raw secrets, or unmasked logs.
• Auth, tenant context, operation guards, confirmation fields, redaction, and structured errors stay in the existing runtime boundary.
• Delete and destructive operations must still use their schema-level delete-safety and exact confirmation fields.

The Appaloft Skill is the agent workflow protocol: it identifies intent, chooses CLI/API/Web/MCP, sequences existing operations, and shapes the final response. MCP is the callable tool layer. When a host has Appaloft MCP tools configured, the skill can prefer tool calls.

When a user says /appaloft help me deploy this repo, /appaloft is the host's skill invocation phrase, not an Appaloft CLI command. Load the skill, then choose MCP, CLI, HTTP/API, or Web based on the active session.