AgentBuilders

Server Details

Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call.

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

6 tools

delete_appInspect

Delete an app and all its data. The name enters a 7-day quarantine period.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	App name to delete

deploy_appInspect

Deploy a full-stack web app. Creates or redeploys an app with static files, optional database, file storage, user auth, and RBAC. Returns a live URL.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	App subdomain name (lowercase alphanumeric + hyphens, 1-63 chars)
`files`	Yes	Map of filename to content string
`public`	No	Make app publicly accessible (default: private with viewKey)
`version`	No	Expected version for optimistic concurrency (CAS)
`rbac_roles`	No	RBAC role definitions: { role_name: { permissions: [...], inherits: [...] } }
`enable_auth`	No	Enable user registration/login for this app
`enable_files`	No	Enable R2 file storage for this app
`database_tables`	No	Database tables: { table_name: { column: 'TEXT'\|'INTEGER'\|'REAL'\|'BLOB' } }
`rbac_default_role`	No	Default role for new users

get_appInspect

Get details of a specific app including URL, capabilities, and version.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	App name

get_viewkeyInspect

Get the viewKey for a private app. Users need this to access the app.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	App name

list_appsInspect

List all apps deployed with your API key.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

update_appInspect

Update app settings (e.g., toggle public/private) without full redeploy.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	App name
`public`	No	Set public accessibility

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.