Skip to Content
Faable DeployGuides & MigrationsDeploy from Cursor

Deploy from Cursor

Add Faable to Cursor once and the agent can create your app, deploy it and read the build logs when something fails, without leaving the editor. Your app runs in the EU at https://<app>.faable.link with free SSL.

1. Connect Faable

The quickest way is the Add to Cursor button on faable.com/mcp . To do it by hand, add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a repository to share it with your team:

{
  "mcpServers": {
    "faable": {
      "url": "https://mcp.faable.com/mcp"
    }
  }
}

2. Sign in

Cursor manages MCP servers from its Customize page. Find faable there and sign in. Your browser opens the Faable consent screen, which shows what is being connected and asks you to choose one project.

No key goes in the file, so .cursor/mcp.json is safe to commit.

3. Deploy

If your code is on GitHub, open it in Cursor and ask the agent:

Deploy this repository to Faable and give me the URL.

The agent finds the repository, creates the app and waits until it is live. From then on, every push deploys on its own.

If it is a local folder, you need the local server, which runs on your machine. Sign in once from a terminal:

npx -y @faable/faable login

Then add it next to the hosted entry:

{
  "mcpServers": {
    "faable-local": {
      "command": "npx",
      "args": ["-y", "@faable/faable", "mcp", "--writes"]
    }
  }
}

And ask:

Deploy this folder to Faable as a new app called my-app.

deploy_directory uploads the folder and builds it. node_modules and .env files stay out, and in a plain folder your .gitignore files apply. It only exists on the local server, because the hosted one cannot see your disk. Once the code is on GitHub, link the repository so a push deploys it.

Things to ask once it is connected

AskWhat happens
”Why did my last deploy fail?”Reads the deployment and its build log, and says whether the cause is your code or Faable’s side
”My app returns 500s. What do the logs say?”Reads the runtime logs of the last 24 hours
”Which paths are failing?”Reads the app’s traffic: status codes, busiest and failing paths
”Add app.example.com to my app”Attaches the domain and returns the CNAME to create at your DNS provider
”Deploy the latest commit”Builds the deploy branch on Faable’s servers and waits until it is live or failed
”Who signed in to my app today?”Reads the logins of your Faable Auth tenant, if you use it

For a value that really is secret, run faable deploy secrets set NAME=value in your own terminal. Cursor can set secrets for you, and Faable never shows the value back, but anything you type in the chat has already gone through your AI provider.

What it can and cannot do

  • The connection acts on one project, the one you chose on the consent screen. It cannot reach your other projects.
  • The hosted server can read, deploy and make reversible changes: create an app, set secrets, add a domain, change the deploy branch. It has no tool that deletes an app. The full list is in the tool catalog .
  • Need reads only? Connect to https://mcp.faable.com/mcp?readonly=1 instead.
  • Logs are treated as data, not instructions. Build output and commit messages can be written by anyone who can push, so they reach the agent marked as untrusted.
  • To disconnect, open your account page  and remove the app under Connected apps. It loses access within a minute.

The usual platform rules apply. Your app has to serve HTTP on $PORT, the Free plan builds Node.js, Python and PHP without a Dockerfile, and a Dockerfile needs Hobby or Pro.

Troubleshooting

  • faable does not appear or shows an error. Check that the JSON is valid, then look at Output → MCP Logs in Cursor for the reason.
  • Cursor asks you to sign in again. Update Cursor first, then sign in from Customize.
  • A repository is missing from the list. Faable only sees repositories the Faable GitHub App is installed on. Ask for your repositories again and the agent returns the install link.
  • plan_required. The repository has a Dockerfile and the project is on Free. Remove the Dockerfile so the managed build applies, or move to Hobby.
  • The deploy failed. Ask why. The answer says whether it is user (your code or configuration) or platform (Faable). The build failures page lists the common causes.

Last updated on

Deploy from Claude CodeDeploy from Codex