Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
faableNo description publishedThis tool published no description. Forge does not invent one.
whoamiThe Faable account this server acts as, the active project and its Auth tenant. Use it first when unsure whether the user is logged in or which project is active.The Faable account this server acts as, the active project and its Auth tenant. Use it first when unsure whether the user is logged in or which project is active.
No input schema was published for this tool.
list_projectsThe user's Faable projects. Apps, domains and Auth tenants live in a project; pass its id as `project` to the other tools.The user's Faable projects. Apps, domains and Auth tenants live in a project; pass its id as `project` to the other tools.
No input schema was published for this tool.
list_appsThe apps of a project, with their live phase, URL and linked repository. Start here to find the app the user means.The apps of a project, with their live phase, URL and linked repository. Start here to find the app the user means.
No input schema was published for this tool.
get_appOne app: phase, URL, repository, deploy branch and mode, detected stack, and its newest deployment (which may have failed while an older one keeps serving). Use it to answer 'is my app up?' or 'what is deployed?'.One app: phase, URL, repository, deploy branch and mode, detected stack, and its newest deployment (which may have failed while an older one keeps serving). Use it to answer 'is my app up?' or 'what is deployed?'.
No input schema was published for this tool.
list_deploymentsRecent deployments of an app, newest first, with phase, commit and the first line of any failure reason. Use it to find the deployment behind 'my last deploy failed'.Recent deployments of an app, newest first, with phase, commit and the first line of any failure reason. Use it to find the deployment behind 'my last deploy failed'.
No input schema was published for this tool.
get_deploymentEverything recorded about one deployment: phase, commit, detected stack, the runnable artifact, the FULL failure reason and, when it failed, `fault` — whether it is the user's to fix (`user`) or Faable's (`platform`). Without `deployment`, the newest one of the app.Everything recorded about one deployment: phase, commit, detected stack, the runnable artifact, the FULL failure reason and, when it failed, `fault` — whether it is the user's to fix (`user`) or Faable's (`platform`). Without `deployment`, the newest one of the app.
No input schema was published for this tool.
get_build_logsThe build output of a deployment — the first thing to read when a deploy failed and the user asks why. The cause is usually at the end. Without `deployment`, the newest one.The build output of a deployment — the first thing to read when a deploy failed and the user asks why. The cause is usually at the end. Without `deployment`, the newest one.
No input schema was published for this tool.
get_runtime_logsWhat the running app printed (last 24 hours, up to 200 lines). Use it when the app is up but misbehaving, or crashes after starting. A deployment retired more than a day ago has none — read its build logs instead.What the running app printed (last 24 hours, up to 200 lines). Use it when the app is up but misbehaving, or crashes after starting. A deployment retired more than a day ago has none — read its build logs instead.
No input schema was published for this tool.
get_app_trafficRequests the app served: status codes, busiest paths and failing paths. Trails reality by up to 15 minutes.Requests the app served: status codes, busiest paths and failing paths. Trails reality by up to 15 minutes.
No input schema was published for this tool.
get_usageThis billing period's usage of a project: plan, apps, domains, deployments and egress.This billing period's usage of a project: plan, apps, domains, deployments and egress.
No input schema was published for this tool.
get_quotaToday's deploy allowance of a project and the builds held waiting for it. Use it when a deploy did not start: a held build is waiting, not failing.Today's deploy allowance of a project and the builds held waiting for it. Use it when a deploy did not start: a held build is waiting, not failing.
No input schema was published for this tool.
list_domainsCustom domains of an app and whether their DNS is verified.Custom domains of an app and whether their DNS is verified.
No input schema was published for this tool.
check_domainDNS diagnostic of one custom domain: the CNAME it expects, what DNS answers today, and why it is not verified yet. `prevalidation_cname.ready` says whether the optional `_acme-challenge` record is in place, so the certificate is issued without waiting for the CNAME; `status.tls_state` is `ok` once…DNS diagnostic of one custom domain: the CNAME it expects, what DNS answers today, and why it is not verified yet. `prevalidation_cname.ready` says whether the optional `_acme-challenge` record is in place, so the certificate is issued without waiting for the CNAME; `status.tls_state` is `ok` once…
No input schema was published for this tool.
list_secretsThe environment variables set on an app. Names only — values are masked and this tool can never reveal them. Use it to check whether a variable the app needs is set.The environment variables set on an app. Names only — values are masked and this tool can never reveal them. Use it to check whether a variable the app needs is set.
No input schema was published for this tool.
list_auth_tenantsThe Faable Auth tenants (user directories) of a project. Most projects have one and every Auth tool uses it; with several, pass the right one as `tenant`.The Faable Auth tenants (user directories) of a project. Most projects have one and every Auth tool uses it; with several, pass the right one as `tenant`.
No input schema was published for this tool.
list_auth_loginsWho logged in to the app's Faable Auth, newest first: one row per login with the user's email, when, from which IP and with which method. Answers 'who logged in recently?' or 'did X log in today?'. For 'how many', use count_auth_users.Who logged in to the app's Faable Auth, newest first: one row per login with the user's email, when, from which IP and with which method. Answers 'who logged in recently?' or 'did X log in today?'. For 'how many', use count_auth_users.
No input schema was published for this tool.
count_auth_usersHow many users of the Auth tenant match: logged in since a time ('how many users logged in today / this week'), signed up since a time ('how many sign-ups this month'), suspended, or all of them. Counts users, not logins.How many users of the Auth tenant match: logged in since a time ('how many users logged in today / this week'), signed up since a time ('how many sign-ups this month'), suspended, or all of them. Counts users, not logins.
No input schema was published for this tool.
list_auth_usersUsers of the Auth tenant. Find one by email or text, list the suspended ones, or sort: `-last_login` (most recent login first), `last_login` (longest without logging in), `-logins_count` (most active), `-createdAt` (newest sign-ups, the default). Sorting by last_login leaves out users who never log…Users of the Auth tenant. Find one by email or text, list the suspended ones, or sort: `-last_login` (most recent login first), `last_login` (longest without logging in), `-logins_count` (most active), `-createdAt` (newest sign-ups, the default). Sorting by last_login leaves out users who never log…
No input schema was published for this tool.
get_auth_userOne user of the Auth tenant by id or email: profile, verification, suspension (and why), last login and login count, and the social identities they sign in with. Use it to confirm who a user is before suspending them, or to see why they can't log in (together with list_auth_logs).One user of the Auth tenant by id or email: profile, verification, suspension (and why), last login and login count, and the social identities they sign in with. Use it to confirm who a user is before suspending them, or to see why they can't log in (together with list_auth_logs).
No input schema was published for this tool.
list_auth_logsThe Auth tenant's audit log, newest first: logins, failed logins (`status: failed`), sign-ups, password resets, admin changes (`type` prefix `admin.user`). Filter by user to answer 'why can't X log in?' — the failed attempts say why.The Auth tenant's audit log, newest first: logins, failed logins (`status: failed`), sign-ups, password resets, admin changes (`type` prefix `admin.user`). Filter by user to answer 'why can't X log in?' — the failed attempts say why.
No input schema was published for this tool.
list_auth_sessionsThe devices a user is signed in on (one row per login session): IP, device, last activity and whether it is still active.The devices a user is signed in on (one row per login session): IP, device, last activity and whether it is still active.
No input schema was published for this tool.
list_auth_connectionsHow users can log in to the Auth tenant: social providers (Google, GitHub…), passwordless (email or SMS codes) and username/password, and which are enabled.How users can log in to the Auth tenant: social providers (Google, GitHub…), passwordless (email or SMS codes) and username/password, and which are enabled.
No input schema was published for this tool.
list_auth_clientsThe applications (OAuth clients) of the Auth tenant: web apps, SPAs, native apps and machine-to-machine clients.The applications (OAuth clients) of the Auth tenant: web apps, SPAs, native apps and machine-to-machine clients.
No input schema was published for this tool.
list_github_reposThe GitHub repositories Faable can deploy: those the Faable GitHub App is installed on. Use it before create_app to find the repository the user means. When the app is not installed (or the repository is missing), give the user `install_url` — installing it is a step in their browser.The GitHub repositories Faable can deploy: those the Faable GitHub App is installed on. Use it before create_app to find the repository the user means. When the app is not installed (or the repository is missing), give the user `install_url` — installing it is a step in their browser.
No input schema was published for this tool.
deploy_appBuild and deploy the latest commit of the app's deploy branch on Faable's servers — the same as a git push. Nothing is uploaded from this machine. With `wait`, returns once it is live (with the URL) or failed (with the reason and whether it is the user's code or Faable's); without it, returns the d…Build and deploy the latest commit of the app's deploy branch on Faable's servers — the same as a git push. Nothing is uploaded from this machine. With `wait`, returns once it is live (with the URL) or failed (with the reason and whether it is the user's code or Faable's); without it, returns the d…
No input schema was published for this tool.
create_appCreate an app from a GitHub repository in a project, link it and start its first deploy (the dashboard's Create & connect). Needs the Faable GitHub App installed on the repository; if the link fails, the new app is removed and the error says what to fix.Create an app from a GitHub repository in a project, link it and start its first deploy (the dashboard's Create & connect). Needs the Faable GitHub App installed on the repository; if the link fails, the new app is removed and the error says what to fix.
No input schema was published for this tool.
redeployRebuild a failed deployment from the source it recorded. Without `deployment`, the newest failed one. Refused for code older than what production serves.Rebuild a failed deployment from the source it recorded. Without `deployment`, the newest failed one. Refused for code older than what production serves.
No input schema was published for this tool.
cancel_deploymentStop a deployment that is still queued or building. Production keeps serving what it served. Without `deployment`, the one in flight.Stop a deployment that is still queued or building. Production keeps serving what it served. Without `deployment`, the one in flight.
No input schema was published for this tool.
set_secretsAdd or update environment variables of an app. The app restarts to apply them when a value changed. Returns the names added, updated and unchanged — never the values.Add or update environment variables of an app. The app restarts to apply them when a value changed. Returns the names added, updated and unchanged — never the values.
No input schema was published for this tool.
add_domainAttach a custom domain to an app. Returns the CNAME record the user must create at their DNS provider; Faable verifies it and issues the certificate on its own. If the domain already serves traffic somewhere else, tell the user to create `prevalidation_cname` (`_acme-challenge.<fqdn>` CNAME) FIRST…Attach a custom domain to an app. Returns the CNAME record the user must create at their DNS provider; Faable verifies it and issues the certificate on its own. If the domain already serves traffic somewhere else, tell the user to create `prevalidation_cname` (`_acme-challenge.<fqdn>` CNAME) FIRST…
No input schema was published for this tool.
configure_repoChange the deploy branch, the monorepo root directory ("" clears it) or the deploy mode (push: every push; ci: once CI tags a release; workflow: the repo's own GitHub workflow). Applies to the next deploy.Change the deploy branch, the monorepo root directory ("" clears it) or the deploy mode (push: every push; ci: once CI tags a release; workflow: the repo's own GitHub workflow). Applies to the next deploy.
No input schema was published for this tool.
link_repoNo description publishedThis tool published no description. Forge does not invent one.
delete_appprivilegedNo description publishedThis tool published no description. Forge does not invent one.
deploy_directoryNo description publishedThis tool published no description. Forge does not invent one.
suspend_auth_userNo description publishedThis tool published no description. Forge does not invent one.
reinstate_auth_userNo description publishedThis tool published no description. Forge does not invent one.
revoke_auth_sessionsNo description publishedThis tool published no description. Forge does not invent one.
update_auth_client_fieldsNo description publishedThis tool published no description. Forge does not invent one.
send_password_setupNo description publishedThis tool published no description. Forge does not invent one.
31 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.