Log inSubmit server
Faable — Deploy & Auth logo

Faable — Deploy & Auth

Deploy GitHub apps, inspect builds and logs, and manage Faable Auth users through an MCP-compatible CLI.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Faable — Deploy & Auth

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "faable-deploy-auth": {
      "command": "npx",
      "args": [
        "-y",
        "@faable/faable"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Hosted endpointLive · 2d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/21/2026, 6:30:32 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.faable.com/mcp

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Faable — Deploy & Auth MCP server exposes Faable Deploy and Faable Auth operations to AI agents over stdio. It uses the Faable CLI and an existing `faable login` session to read apps, deployments, build and runtime logs, and authentication data. By default, agents can also call `deploy_app`; enabling `--writes` adds selected deployment and configuration changes. Reach for it when an agent needs to investigate or operate Faable-hosted applications and identity tenants.

Use cases

  • Deploy an application from its latest commit
  • Inspect failed build and runtime logs
  • Review deployment traffic and status
  • Manage Faable Auth users and OAuth clients
  • Query audit logs for authentication events

Key features

  • Stdio MCP transport
  • Application and deployment inspection
  • Latest-commit deployment
  • Optional deployment configuration writes
  • Faable Auth administration
  • Structured JSON output and errors

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · @faable/faable (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit2d agoMost recent push to the default branch.

How Faable — Deploy & Auth works

What Faable — Deploy & Auth does

Faable — Deploy & Auth connects an MCP-compatible client to the Faable platform through the Faable CLI. It covers two related areas: Faable Deploy for application delivery and operations, and Faable Auth for identity-tenant administration. The repository positions this listing in the 💻 Developer Tools category.

For deployment work, an agent can inspect applications, deployment status, build output, runtime logs, deployment history, traffic, usage, quotas, and detected application details. It can also deploy the latest commit with the exposed deploy_app capability. The underlying CLI supports applications sourced from GitHub repositories, as well as deployments from a local directory.

For authentication administration, the CLI includes user listings and lookups, suspension and reinstatement, login-flow actions, OAuth client management, and read-only audit-log access. Auth commands target a Faable Auth tenant using its URL.

How it works

The MCP entry point is the CLI command faable mcp, which communicates over stdio. A client starts the command and the server uses the session created by faable login. The README specifically names Claude Code and Cursor, while also describing the interface as usable by MCP clients generally.

Read operations are enabled by default, together with deploy_app. Passing --writes exposes reversible changes such as creating an application from a repository, setting environment variables, adding a domain, retrying or cancelling a build, and changing deployment settings. Secret values are not returned, and log content is marked as data rather than instructions.

Setup and configuration

Install the CLI globally with npm i -g @faable/faable, then authenticate with faable login. A client can register the server with:

Terminal
claude mcp add faable -- npx -y @faable/faable mcp

Use faable mcp --writes when the agent needs the additional write capabilities. Authentication tenant operations require an auth URL supplied with --auth-url or through FAABLE_AUTH_URL.

For scripted or agent-driven CLI use, set FAABLE_NONINTERACTIVE=1 or pass --non-interactive. In that mode, confirmations fail unless --yes is supplied, and deployment launch requires explicit app, working-directory, and confirmation arguments. Secret input can be provided through stdin rather than command-line arguments.

Tools and capabilities

Faable — Deploy & Auth provides access to:

  • Application, project, deployment, status, log, traffic, usage, and quota inspection.
  • Deployment of an app’s latest commit through deploy_app.
  • Optional writes for repositories, environment variables, domains, build retries and cancellation, and deploy settings.
  • Faable Auth user, login-action, OAuth-client, and audit-log operations.
  • JSON-oriented CLI output, pagination, structured errors, and no-op results for automation.

Limitations and notes

The MCP server runs locally as a stdio process and depends on the Faable CLI and its authentication session. Write capabilities are opt-in rather than enabled by default. Secret values are intentionally excluded from returned data, and noninteractive workflows must handle confirmation requirements explicitly.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Faable — Deploy & Auth

Faable — Deploy & Auth is an MCP server that connects AI clients to Faable Deploy and Faable Auth through the Faable CLI. Its main tools read apps, deployments, build and runtime logs, users, OAuth clients, and audit logs, while `deploy_app` deploys the latest commit; optional writes manage selected settings.

Install it with `npm i -g @faable/faable`, authenticate using `faable login`, and register `faable mcp` with your MCP client. The README gives `claude mcp add faable -- npx -y @faable/faable mcp` as the Claude setup command.

Yes, Cursor is explicitly named as a supported MCP client. Configure Cursor to start the stdio command `npx -y @faable/faable mcp` after authenticating with `faable login`.

Start the server with `faable mcp --writes`. This adds reversible operations such as creating an app from a repository, setting environment variables, adding a domain, retrying or cancelling a build, and changing deployment settings.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFaable — Deploy & Auth AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/faable-deploy-auth?style=directory)](https://allmcps.com/mcp/faable-deploy-auth)
HTML Embed
<a href="https://allmcps.com/mcp/faable-deploy-auth"><img src="https://allmcps.com/api/badge/faable-deploy-auth?style=directory" alt="Faable — Deploy & Auth on AllMCPs" /></a>