# Faable — Deploy & Auth [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/faablecloud/faable  
**GitHub Stars:** 1  
**npm Downloads (last month):** 5878  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/faable-deploy-auth

## Description
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "faable-deploy-auth": {
    "command": "npx",
    "args": ["-y","@faable/faable"]
  }
}
```

## Documentation

## What Faable — Deploy & Auth does

Faable — Deploy & Auth connects an MCP client to the Faable platform's deployment and identity-management functions. It lets an agent inspect applications, deployments, statuses, build output, runtime logs, traffic, usage, quotas, and deployment configuration. The server also exposes Faable Auth administration for users, login-flow actions, OAuth clients, and audit logs.

The default MCP configuration provides read operations and `deploy_app`, which builds the latest commit on the server. A separate write mode adds selected reversible deployment changes: creating an app from a repository, setting environment variables, adding a custom domain, retrying or canceling a build, and changing deployment settings. Secret values are not returned, and log content is marked as data rather than instructions.

## How it works

The `faable mcp` command starts the CLI as an MCP server over standard input and output. Authentication uses the existing Faable CLI session created by `faable login`; the same session can be used for deployment and Faable Auth administration. For a Faable Auth tenant, supply its URL with `--auth-url` or `FAABLE_AUTH_URL`.

A client can use the server to answer operational questions such as why a deployment failed by reading deployment state and logs, then invoke the available deployment operation. The CLI supports application selection by ID, name, or slug. Faable Auth user listings support FaableQL filters, while audit-log and other list operations can be filtered through their command options.

## Setup and configuration

Install the CLI globally with npm:

```bash
npm i -g @faable/faable
```

Authenticate before starting the MCP server:

```bash
faable login
```

Add it to Claude Code with:

```bash
claude mcp add faable -- npx -y @faable/faable mcp
```

The standard server starts without write access beyond `deploy_app`. Pass `--writes` to expose the additional reversible write operations:

```bash
npx -y @faable/faable mcp --writes
```

For non-interactive automation, set `FAABLE_NONINTERACTIVE=1` or pass the equivalent CLI option. In that mode, confirmations fail unless `--yes` is supplied, and deployment launch requires explicit app, working-directory, and confirmation parameters. Secret values should be provided through stdin rather than command-line arguments.

## Tools and capabilities

- Read Faable apps, deployment records, statuses, inspection data, logs, traffic, usage, and quotas.
- Deploy the latest commit with `deploy_app`.
- Create apps from GitHub repositories, including their first deployment, when writes are enabled.
- Set deployment environment variables, add domains, retry or cancel builds, and change deployment settings.
- List and administer Faable Auth users, including suspension and reinstatement.
- Create, update, and remove login-flow actions.
- Create and remove OAuth clients, with optional access to client secrets through the CLI operation.
- Read filtered Faable Auth audit logs.

## Limitations and notes

The MCP transport is stdio, so the client must launch the CLI process. Authentication depends on a valid Faable login session; CI workflows can use OIDC without an interactive login. The server does not return secret values, and its default configuration does not expose the additional write operations. Destructive operations are not exposed through the MCP write mode described here.

List responses and write results follow the CLI's JSON conventions when JSON output is requested. Failures use structured error data and can indicate an expired session, missing permissions, a required app, a required confirmation, or an invalid request.

_Full upstream README: https://allmcps.com/mcp/faable-deploy-auth/readme_