Faber MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| faber_check_appC | Check if an app exists on the Faber server and get its details |
| faber_list_appsC | List all deployed apps on the Faber server |
| faber_create_stackA | Create a full application stack (app + domain + database + SSL + .env). Handles GitHub Device Flow OAuth for automatic deploy key setup if configured on server. First call shows a preview - set confirm: true to execute. |
| faber_deployC | Trigger a zero-downtime deployment for an app |
| faber_get_deploy_keyA | Retrieve the SSH public key for an app (used for manual deploy key setup) |
| faber_server_statusC | Get server health and service status |
| faber_service_restartC | Restart a system service (nginx, php, mysql, supervisor, redis) |
| faber_list_domainsC | List all configured domains on the Faber server |
| faber_create_domainC | Create and assign a domain to an app (includes SSL setup) |
| faber_list_databasesC | List all databases on the Faber server |
| faber_create_databaseC | Create a new MySQL database with a dedicated user |
| faber_list_releasesC | List all available releases for an app |
| faber_rollbackC | Roll back an app to a previous release |
| faber_webhook_logsC | View webhook execution logs |
| faber_app_logsC | View Laravel application logs for an app |
| faber_get_envC | Read the .env file for an app (read-only) |
| faber_set_env_varC | Set a specific environment variable in an app's .env file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, such as faber_create_database for database creation, faber_deploy for deployments, and faber_set_env_var for environment variable management. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one based on the task.
All tool names follow a consistent verb_noun pattern with the prefix 'faber_' and snake_case throughout, such as faber_list_apps, faber_create_domain, and faber_get_env. This predictable naming scheme enhances readability and usability for agents.
With 17 tools, the count is slightly high but reasonable for the comprehensive scope of managing a Faber server, covering app deployment, domain setup, database management, and server operations. It is well-scoped with each tool serving a distinct function, though it borders on being heavy.
The tool set provides complete CRUD and lifecycle coverage for the Faber server domain, including creation (e.g., faber_create_stack), listing (e.g., faber_list_apps), updates (e.g., faber_set_env_var), and deletion implicitly through operations like rollback. There are no obvious gaps, and agents can handle full workflows from setup to maintenance.