Deployxa MCP server lets agents inspect, deploy, manage, and troubleshoot cloud applications and databases. Use deployxa_list_projects to discover existing projects, deployxa_get_deployment_logs and deployxa_diagnose_deployment to investigate failures, and deployxa_create_deployment to trigger new releases. Mutating tools modify production resources; confirm destructive operations before execution.
Discoverability
1/6 passed1 of 6 passed17/100
Client listings and public setup information.
mcp.json or server-card.json
Either mcp.json or an MCP Server Card declaring this endpoint passes.
The manifest declares this MCP server's exact endpoint.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
List projects accessible to the organization. Without pagination arguments, returns an array of project records; supplying limit or cursor returns a page with data and nextCursor. Use the returned IDs to select projects for other tools.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Number of records to include per page.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
Pagination token obtained from nextCursor of a previous listing to retrieve the next page.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_list_projects",
"title": "List Projects",
"description": "List projects accessible to the organization. Without pagination arguments, returns an array of project records; supplying limit or cursor returns a page with data and nextCursor. Use the returned IDs to select projects for other tools.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Number of records to include per page."
},
"cursor": {
"type": "string",
"minLength": 1,
"description": "Pagination token obtained from nextCursor of a previous listing to retrieve the next page."
}
}
},
"annotations": {
"title": "List Projects",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Create project configuration connected to a Git repository, including branch, framework, build strategy, and readiness settings. Adds a project to the organization and returns its saved record. Confirmation is optional under the tool policy.
Describe the returned information so the agent knows whether it will answer the request.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
name
Name assigned to identify the project in the workspace and dashboard.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
repositoryUrl
Git repository location containing application source code to deploy.
Clear enough to supply this argument.
branch
Default Git branch to build and deploy; creation uses main when omitted.
Clear enough to supply this argument.
framework
Application framework preset; when omitted, the framework is automatically detected from project files.
Clear enough to supply this argument.
rootDirectory
Subdirectory path containing project source code; when omitted, the repository root directory is used.
Clear enough to supply this argument.
healthCheckPath
HTTP path probed during deployment to verify container readiness; when omitted at creation, / is stored.
Clear enough to supply this argument.
healthCheckExpectedCodes
HTTP status codes accepted by readiness probes, written as comma-separated codes or inclusive ranges, e.g. 200,204,300-399. Creation stores 200-399 when omitted.
Clear enough to supply this argument.
healthCheckTimeoutSeconds
Time allowed for each readiness probe, in seconds; creation stores 5 seconds when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
healthCheckGracePeriodSeconds
Container startup warmup period before readiness probes, in seconds; creation stores 0 when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
buildStrategy
Mechanism used by the build pipeline to compile source code into container images.
Explain what happens when this optional value is omitted.
dockerfilePath
Path to the Dockerfile relative to repository root directory (default: Dockerfile).
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Update project name, branch, source directory, readiness settings, and build configuration for future deployments. Omitted settings retain their current values. The current API ignores repositoryUrl and framework updates. Returns the saved project record; confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
name
New human-readable display name for the project to replace the current name in the dashboard and CLI.
Clear enough to supply this argument.
repositoryUrl
Git repository location submitted with the update; the current API ignores this field and retains the existing repository.
Clear enough to supply this argument.
branch
Updated default Git branch to target for future deployments; when omitted, the current branch setting remains unchanged.
Clear enough to supply this argument.
framework
Application framework preset submitted with the update; the current API ignores this field and retains the existing framework.
Clear enough to supply this argument.
rootDirectory
Subdirectory path containing project source code; when omitted, the current root directory setting remains unchanged.
Clear enough to supply this argument.
healthCheckPath
HTTP path probed during deployment to verify readiness; omission retains the current setting.
Clear enough to supply this argument.
healthCheckExpectedCodes
HTTP status codes accepted by readiness probes, written as comma-separated codes or inclusive ranges, e.g. 200,204,300-399. Omission retains the current setting.
Clear enough to supply this argument.
healthCheckTimeoutSeconds
Time allowed for each readiness probe, in seconds; omission retains the current setting.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
healthCheckGracePeriodSeconds
Container startup warmup period before readiness probes, in seconds; omission retains the current setting.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
buildStrategy
Mechanism used by the build pipeline to compile source code into container images.
Clear enough to supply this argument.
dockerfilePath
Dockerfile path relative to the repository root, stored in project configuration; omission retains the current setting and an empty string clears it.
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_update_project",
"title": "Update Project",
"description": "Update project name, branch, source directory, readiness settings, and build configuration for future deployments. Omitted settings retain their current values. The current API ignores repositoryUrl and framework updates. Returns the saved project record; confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"name": {
"type": "string",
"description": "New human-readable display name for the project to replace the current name in the dashboard and CLI."
},
"branch": {
"type": "string",
"description": "Updated default Git branch to target for future deployments; when omitted, the current branch setting remains unchanged."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"framework": {
"type": "string",
"description": "Application framework preset submitted with the update; the current API ignores this field and retains the existing framework."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
},
"buildStrategy": {
"enum": [
"auto",
"dockerfile",
"buildpack",
"nixpacks"
],
"type": "string",
"description": "Mechanism used by the build pipeline to compile source code into container images."
},
"repositoryUrl": {
"type": "string",
"format": "uri",
"description": "Git repository location submitted with the update; the current API ignores this field and retains the existing repository."
},
"rootDirectory": {
"type": "string",
"description": "Subdirectory path containing project source code; when omitted, the current root directory setting remains unchanged."
},
"dockerfilePath": {
"type": "string",
"description": "Dockerfile path relative to the repository root, stored in project configuration; omission retains the current setting and an empty string clears it."
},
"healthCheckPath": {
"type": "string",
"description": "HTTP path probed during deployment to verify readiness; omission retains the current setting."
},
"healthCheckExpectedCodes": {
"type": "string",
"description": "HTTP status codes accepted by readiness probes, written as comma-separated codes or inclusive ranges, e.g. 200,204,300-399. Omission retains the current setting."
},
"healthCheckTimeoutSeconds": {
"type": "integer",
"maximum": 60,
"minimum": 1,
"description": "Time allowed for each readiness probe, in seconds; omission retains the current setting."
},
"healthCheckGracePeriodSeconds": {
"type": "integer",
"maximum": 300,
"minimum": 0,
"description": "Container startup warmup period before readiness probes, in seconds; omission retains the current setting."
}
}
},
"annotations": {
"title": "Update Project",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Permanently delete a project and all associated deployments, containers, custom domains, environment variables, and build artifacts. This operation is irreversible and immediately tears down live infrastructure. Requires confirmed: true. Returns confirmation message.
The description explains the capability, when to use it, and what to expect.
Inputs74/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_delete_project",
"title": "Delete Project",
"description": "Permanently delete a project and all associated deployments, containers, custom domains, environment variables, and build artifacts. This operation is irreversible and immediately tears down live infrastructure. Requires confirmed: true. Returns confirmation message.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Confirmation of execution; when omitted or false, destructive actions are blocked without making changes."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
}
}
},
"annotations": {
"title": "Delete Project",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
List all deployments for a project, returning an array of deployments with deployment IDs, status (queued, building, running, failed, cancelled), Git branch, commit hash, commit message, creator, preview URLs, and timestamps.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
List all deployments across the organization, returning deployment IDs, project IDs, statuses, commit metadata, URLs, and timestamps. Supports pagination via limit and cursor.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Number of records to include per page.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
Pagination token obtained from nextCursor of a previous listing to retrieve the next page.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Retrieve deployment metadata including current state (building, running, failed), live URL, Git commit hash, branch, trigger source, build duration, milestone timestamps, and diagnostic summaries.
The description explains the capability, when to use it, and what to expect.
Inputs82/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Run automated AI root-cause diagnostics on a failed deployment, returning the diagnosed failure category, summary explanation, root cause analysis, offending log lines, and actionable remediation steps.
The description explains the capability, when to use it, and what to expect.
Inputs78/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Analyze deployment telemetry, build outputs, and failure events to answer operational questions with evidence-based root-cause explanations and suggested fixes.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
question
The operational question to answer using deployment logs, events, and diagnostics.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Read a page of deployment log lines with messages, timestamps, stream labels, and seq sequence numbers. Use the last line's seq as cursor to retrieve subsequent lines for the same stream selection; tail selects the latest matching lines.
Describe the returned information so the agent knows whether it will answer the request.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
stream
Log selection: all includes every stream; build excludes messages beginning with [Runtime]; stdout selects normal output and stderr selects error output.
Clear enough to supply this argument.
cursor
Sequence number of the last returned log line (its seq field); retrieves subsequent lines for the same stream selection.
Clear enough to supply this argument.
limit
Number of log lines to retrieve in this request.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
tail
When true, fetches the latest lines from the end of the log stream.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_get_deployment_logs",
"title": "Get Deployment Logs",
"description": "Read a page of deployment log lines with messages, timestamps, stream labels, and seq sequence numbers. Use the last line's seq as cursor to retrieve subsequent lines for the same stream selection; tail selects the latest matching lines.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId."
},
"tail": {
"type": "boolean",
"default": false,
"description": "When true, fetches the latest lines from the end of the log stream."
},
"limit": {
"type": "integer",
"default": 200,
"maximum": 1000,
"minimum": 1,
"description": "Number of log lines to retrieve in this request."
},
"cursor": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Sequence number of the last returned log line (its seq field); retrieves subsequent lines for the same stream selection."
},
"stream": {
"enum": [
"all",
"build",
"stdout",
"stderr"
],
"type": "string",
"default": "all",
"description": "Log selection: all includes every stream; build excludes messages beginning with [Runtime]; stdout selects normal output and stderr selects error output."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment."
}
}
},
"annotations": {
"title": "Get Deployment Logs",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Retrieve real-time progression of an active deployment, returning the active lifecycle stage (cloning, building, provisioning, health-checking), completed milestones, elapsed duration, and overall percentage.
The description explains the capability, when to use it, and what to expect.
Inputs76/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Retrieve timestamped lifecycle milestones and state transitions for a deployment, returning stage start/finish times, error occurrences, and total execution duration.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Trigger a new deployment build from a Git branch or pull request. Mutates project state by queuing a build, building container images, and provisioning new workloads. Requires projectId and confirmed: true. Returns the queued DeploymentDto.
The description explains the capability, when to use it, and what to expect.
Inputs82/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
branch
Git branch to check out and deploy; when omitted, defaults to the project default branch.
Clear enough to supply this argument.
isPreview
Controls deployment environment tier; when true, creates an ephemeral preview deployment with an isolated staging URL; when omitted or false, provisions a production release.
Clear enough to supply this argument.
repoFullName
Full repository name (e.g. "org/repo") if overriding default project repo.
Clear enough to supply this argument.
prNumber
Associated pull request number; when omitted, the deployment is treated as a branch deployment without pull request linkage.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_create_deployment",
"title": "Create Deployment",
"description": "Trigger a new deployment build from a Git branch or pull request. Mutates project state by queuing a build, building container images, and provisioning new workloads. Requires projectId and confirmed: true. Returns the queued DeploymentDto.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"branch": {
"type": "string",
"description": "Git branch to check out and deploy; when omitted, defaults to the project default branch."
},
"prNumber": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Associated pull request number; when omitted, the deployment is treated as a branch deployment without pull request linkage.",
"exclusiveMinimum": 0
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Confirmation of execution; when omitted or false, destructive actions are blocked without making changes."
},
"isPreview": {
"type": "boolean",
"description": "Controls deployment environment tier; when true, creates an ephemeral preview deployment with an isolated staging URL; when omitted or false, provisions a production release."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
},
"repoFullName": {
"type": "string",
"description": "Full repository name (e.g. \"org/repo\") if overriding default project repo."
}
}
},
"annotations": {
"title": "Create Deployment",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Cancel an active or queued deployment build. Mutates deployment lifecycle by immediately terminating build workers and stopping provisioning. Cannot be undone; a new deployment must be created to retry. Requires deploymentId and confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_cancel_deployment",
"title": "Cancel Deployment",
"description": "Cancel an active or queued deployment build. Mutates deployment lifecycle by immediately terminating build workers and stopping provisioning. Cannot be undone; a new deployment must be created to retry. Requires deploymentId and confirmed: true.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Confirmation of execution; when omitted or false, destructive actions are blocked without making changes."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment."
}
}
},
"annotations": {
"title": "Cancel Deployment",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Roll back a project to a previous deployment version. Mutates production edge routing to redirect traffic to the target deployment and activates its workload. Requires deploymentId and confirmed: true. Returns the activated DeploymentDto.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
confirmed
Explicit confirmation to execute the deployment rollback; when omitted or false, the operation is rejected without changing running containers.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_rollback_deployment",
"title": "Rollback Deployment",
"description": "Roll back a project to a previous deployment version. Mutates production edge routing to redirect traffic to the target deployment and activates its workload. Requires deploymentId and confirmed: true. Returns the activated DeploymentDto.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Explicit confirmation to execute the deployment rollback; when omitted or false, the operation is rejected without changing running containers."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment."
}
}
},
"annotations": {
"title": "Rollback Deployment",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Promote a successful deployment in the organization to production; the API requires SUCCESS status. Configures the generated production domain and SSL when a container is present, clears the preview flag, and updates the project URL. Bills and stops containers from other successful production deployments, which can interrupt those workloads. Returns success, a message, and the updated deployment. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_promote_deployment",
"title": "Promote Deployment",
"description": "Promote a successful deployment in the organization to production; the API requires SUCCESS status. Configures the generated production domain and SSL when a container is present, clears the preview flag, and updates the project URL. Bills and stops containers from other successful production deployments, which can interrupt those workloads. Returns success, a message, and the updated deployment. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment."
}
}
},
"annotations": {
"title": "Promote Deployment",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
List environment variables configured for a project, returning variable IDs, key names, branch associations, and timestamps with secret values safely redacted.
The description explains the capability, when to use it, and what to expect.
Inputs65/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Create or update a project environment variable, encrypting its value at rest. The current API saves variables globally across branches and does not trigger a redeployment. Returns the variable ID, key, and save message, without the value. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
key
The environment variable name/key (e.g. DATABASE_URL or API_KEY).
Clear enough to supply this argument.
value
Secret or configuration content stored for this variable and injected into the container environment.
Clear enough to supply this argument.
branch
Git branch submitted with the variable; the current API ignores this field and saves the variable globally across branches.
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_set_environment",
"title": "Set Environment Variable",
"description": "Create or update a project environment variable, encrypting its value at rest. The current API saves variables globally across branches and does not trigger a redeployment. Returns the variable ID, key, and save message, without the value. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"key",
"value"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"key": {
"type": "string",
"minLength": 1,
"description": "The environment variable name/key (e.g. DATABASE_URL or API_KEY)."
},
"value": {
"type": "string",
"minLength": 1,
"description": "Secret or configuration content stored for this variable and injected into the container environment."
},
"branch": {
"type": "string",
"description": "Git branch submitted with the variable; the current API ignores this field and saves the variable globally across branches."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
}
}
},
"annotations": {
"title": "Set Environment Variable",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Permanently delete an environment variable from a project. Mutates project environment configuration and may disrupt application runtime if the variable is required. Requires environmentId and confirmed: true. Returns confirmation message.
Resolve contradictions between the description, input schema, and annotations.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
environmentId
Environment variable identifier obtained from deployxa_list_environment.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Environment variable to delete; use its identifier as id in place of environmentId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
List custom domains mapped to a project, returning domain names, verification status, SSL certificate status, primary routing flags, and required DNS target records.
The description explains the capability, when to use it, and what to expect.
Inputs78/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Create or update a custom domain mapping for a project and start DNS verification in the background. Configure the domain DNS records using the returned cnameTarget and verificationToken; routing and SSL activation depend on verification. Returns the saved mapping with DNS and SSL status. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_add_domain",
"title": "Add Custom Domain",
"description": "Create or update a custom domain mapping for a project and start DNS verification in the background. Configure the domain DNS records using the returned cnameTarget and verificationToken; routing and SSL activation depend on verification. Returns the saved mapping with DNS and SSL status. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"domain": {
"type": "string",
"minLength": 1,
"description": "Custom domain name to route to the project (e.g. app.example.com)."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
}
}
},
"annotations": {
"title": "Add Custom Domain",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Trigger verification of custom domain DNS ownership and SSL certificate issuance, returning an object with dnsVerified boolean status, sslStatus (active, pending, or failed), and error details if verification fails.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
confirmed
Acknowledgment of the verification request; this write operation proceeds whether confirmation is supplied or omitted.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Permanently remove a custom domain mapping from a project. Mutates edge routing by disabling ingress traffic and releasing associated SSL certificates. Requires projectId, domain, and confirmed: true. Returns confirmation message.
Resolve contradictions between the description, input schema, and annotations.
Inputs75/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Remove a custom domain mapping from project routing (alias for deployxa_delete_domain). Immediately disables traffic routing for this hostname. Requires projectId, domain, and confirmed: true. Returns confirmation message.
Resolve contradictions between the description, input schema, and annotations.
Inputs75/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Evaluate production release readiness for a project, returning overall readiness score, pass/fail status for health checks, environment variables, domain configuration, and security settings.
The description explains the capability, when to use it, and what to expect.
Inputs78/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Retrieve production monitoring summary for a project, returning real-time service health, uptime percentage, average response latency, request volume, error rates, and active alerts.
The description explains the capability, when to use it, and what to expect.
Inputs74/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Retrieve resource utilization metrics for a project, returning compute CPU percentage, container memory consumption in MB, persistent disk usage in GB, and network bandwidth in bytes.
The description explains the capability, when to use it, and what to expect.
Inputs73/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
List generated build and deployment output artifacts across a project, returning artifact IDs, filenames, byte sizes, MIME types, creation timestamps, and download links.
The description explains the capability, when to use it, and what to expect.
Inputs73/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Query the Deployxa AI assistant with project configuration, runtime logs, and deployment context to resolve operational questions and generate remediation steps.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
deploymentId
Deployment context to scope questions to, enabling the assistant to reference specific build logs and errors; when omitted, questions apply to overall project state.
Clear enough to supply this argument.
message
User prompt or operational query sent to the Deployxa AI assistant.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_chat_assistant",
"title": "Chat with Assistant",
"description": "Query the Deployxa AI assistant with project configuration, runtime logs, and deployment context to resolve operational questions and generate remediation steps.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"message"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"message": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "User prompt or operational query sent to the Deployxa AI assistant."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment context to scope questions to, enabling the assistant to reference specific build logs and errors; when omitted, questions apply to overall project state."
}
}
},
"annotations": {
"title": "Chat with Assistant",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Provision a managed database container and persistent storage for an existing project, and save its connection variables in the project environment. Supports PostgreSQL, MySQL, and Redis; the accepted sqlite input currently provisions PostgreSQL. Returns database metadata with secrets redacted. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs84/100
Explain what happens when this optional value is omitted.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
name
Human-readable label for identifying the database instance in connection strings and dashboard.
Clear enough to supply this argument.
engine
Database software to provision; omission initializes PostgreSQL. The current provisioner also maps sqlite to PostgreSQL.
Clear enough to supply this argument.
cpuLimitCores
Compute capacity allocated to the database, in CPU cores; the provisioner allocates one core when omitted.
Clear enough to supply this argument.
memoryLimitMb
System memory allocated to this database instance, in megabytes.
Explain what happens when this optional value is omitted.
storageLimitGb
Persistent disk storage limit in gigabytes (GB).
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_create_database",
"title": "Create Managed Database",
"description": "Provision a managed database container and persistent storage for an existing project, and save its connection variables in the project environment. Supports PostgreSQL, MySQL, and Redis; the accepted sqlite input currently provisions PostgreSQL. Returns database metadata with secrets redacted. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"name": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "Human-readable label for identifying the database instance in connection strings and dashboard."
},
"engine": {
"enum": [
"postgres",
"mysql",
"sqlite",
"redis"
],
"type": "string",
"default": "postgres",
"description": "Database software to provision; omission initializes PostgreSQL. The current provisioner also maps sqlite to PostgreSQL."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
},
"cpuLimitCores": {
"type": "number",
"maximum": 64,
"description": "Compute capacity allocated to the database, in CPU cores; the provisioner allocates one core when omitted.",
"exclusiveMinimum": 0
},
"memoryLimitMb": {
"type": "integer",
"maximum": 131072,
"description": "System memory allocated to this database instance, in megabytes.",
"exclusiveMinimum": 0
},
"storageLimitGb": {
"type": "integer",
"maximum": 2048,
"description": "Persistent disk storage limit in gigabytes (GB).",
"exclusiveMinimum": 0
}
}
},
"annotations": {
"title": "Create Managed Database",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Retrieve performance telemetry for a database instance, returning CPU utilization percentage, memory consumption percentage, storage disk usage, active client connections, and connection limits.
The description explains the capability, when to use it, and what to expect.
Inputs76/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
databaseId
Database instance identifier obtained from deployxa_list_databases or deployxa_create_database.
Clear enough to supply this argument.
id
Managed database instance to inspect; use its identifier as id in place of databaseId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
List automated and on-demand snapshot backups for a database instance, returning backup IDs, snapshot sizes, creation timestamps, storage status, and expiration dates.
The description explains the capability, when to use it, and what to expect.
Inputs74/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
databaseId
Database instance identifier obtained from deployxa_list_databases or deployxa_create_database.
Clear enough to supply this argument.
id
Managed database instance to inspect; use its identifier as id in place of databaseId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
List configured database user roles for a database instance, returning user IDs, usernames, granted roles/privileges, and active connection counts without exposing passwords.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Resolve the mismatch between this description and its schema constraints.
databaseId
Database instance identifier obtained from deployxa_list_databases or deployxa_create_database.
Clear enough to supply this argument.
id
Managed database instance to inspect; use its identifier as id in place of databaseId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
List Git repositories accessible through the connected GitHub account or Git provider, returning repository names, full names, clone URLs, default branches, and access permissions.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Retrieve recommended DNS record configurations for custom domains, returning necessary A, CNAME, and TXT records, target IP addresses, canonical hostnames, and TTL recommendations.
The description explains the capability, when to use it, and what to expect.
Inputs65/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
domain
Domain name to filter DNS configuration instructions for; when omitted, DNS guidance is returned for all custom domains attached to the project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_get_dns_guidance",
"title": "Get DNS Guidance",
"description": "Retrieve recommended DNS record configurations for custom domains, returning necessary A, CNAME, and TXT records, target IP addresses, canonical hostnames, and TTL recommendations.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"domain": {
"type": "string",
"minLength": 1,
"description": "Domain name to filter DNS configuration instructions for; when omitted, DNS guidance is returned for all custom domains attached to the project."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
}
}
},
"annotations": {
"title": "Get DNS Guidance",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
List domain registration and renewal orders placed by the organization, returning order IDs, domain names, order types, payment amounts, fulfillment status, and timestamps.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Purchase and register a domain using paid organization credits and attach it to a project. Deducts credits and registers the domain with the upstream registrar; promotional credits cannot fund domains. A project identifier is needed via projectId or id, and contact details are needed for the first purchase. Requires confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Explain what happens when this optional value is omitted.
projectId
Project to attach and route the purchased domain to; id can supply the same identifier. Omitting both identifiers rejects the call before purchase.
Clear enough to supply this argument.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
durationYears
Length of the initial registration, in years; the API registers for one year when omitted.
Clear enough to supply this argument.
privacy
Enables WHOIS privacy protection to hide registrant contact information; when omitted, registrar default privacy settings apply.
Clear enough to supply this argument.
premium
Whether to allow purchasing premium domains at higher registry pricing tiers.
Explain what happens when this optional value is omitted.
registrant › name
Full legal name of the registrant or organization contact.
Clear enough to supply this argument.
registrant › email
Registrant contact email address for domain ownership notices.
Clear enough to supply this argument.
registrant › companyName
Company or organization name.
Explain what happens when this optional value is omitted.
registrant › address
Physical street location of the domain owner for WHOIS compliance.
Clear enough to supply this argument.
registrant › city
City for registrant address.
Clear enough to supply this argument.
registrant › state
State or province for registrant address.
Clear enough to supply this argument.
registrant › country
Country of residence or incorporation for the domain owner, following ISO 3166-1 alpha-2 standards.
Clear enough to supply this argument.
registrant › postalCode
Postal/ZIP code for registrant address.
Clear enough to supply this argument.
registrant › phoneCountryCode
International dialing prefix for contacting the registrant by phone.
Clear enough to supply this argument.
registrant › phone
Contact phone number for domain registration records.
Clear enough to supply this argument.
confirmed
Authorization to deduct organization credits and register the domain with the registrar; when omitted or false, registration is aborted.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_purchase_domain",
"title": "Purchase Domain",
"description": "Purchase and register a domain using paid organization credits and attach it to a project. Deducts credits and registers the domain with the upstream registrar; promotional credits cannot fund domains. A project identifier is needed via projectId or id, and contact details are needed for the first purchase. Requires confirmed: true.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"domain": {
"type": "string",
"minLength": 1,
"description": "Custom domain name to route to the project (e.g. app.example.com)."
},
"premium": {
"type": "boolean",
"description": "Whether to allow purchasing premium domains at higher registry pricing tiers."
},
"privacy": {
"type": "boolean",
"description": "Enables WHOIS privacy protection to hide registrant contact information; when omitted, registrar default privacy settings apply."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Authorization to deduct organization credits and register the domain with the registrar; when omitted or false, registration is aborted."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project to attach and route the purchased domain to; id can supply the same identifier. Omitting both identifiers rejects the call before purchase."
},
"registrant": {
"type": "object",
"required": [
"name",
"email",
"address",
"city",
"state",
"country",
"postalCode",
"phoneCountryCode",
"phone"
],
"properties": {
"city": {
"type": "string",
"minLength": 1,
"description": "City for registrant address."
},
"name": {
"type": "string",
"minLength": 1,
"description": "Full legal name of the registrant or organization contact."
},
"email": {
"type": "string",
"minLength": 1,
"description": "Registrant contact email address for domain ownership notices."
},
"phone": {
"type": "string",
"minLength": 1,
"description": "Contact phone number for domain registration records."
},
"state": {
"type": "string",
"minLength": 1,
"description": "State or province for registrant address."
},
"address": {
"type": "string",
"minLength": 1,
"description": "Physical street location of the domain owner for WHOIS compliance."
},
"country": {
"type": "string",
"minLength": 1,
"description": "Country of residence or incorporation for the domain owner, following ISO 3166-1 alpha-2 standards."
},
"postalCode": {
"type": "string",
"minLength": 1,
"description": "Postal/ZIP code for registrant address."
},
"companyName": {
"type": "string",
"description": "Company or organization name."
},
"phoneCountryCode": {
"type": "string",
"minLength": 1,
"description": "International dialing prefix for contacting the registrant by phone."
}
},
"description": "Contact details for the first domain purchase; omission reuses the organization registrar account if one already exists, otherwise the API rejects the purchase."
},
"durationYears": {
"type": "integer",
"maximum": 10,
"minimum": 1,
"description": "Length of the initial registration, in years; the API registers for one year when omitted."
}
}
},
"annotations": {
"title": "Purchase Domain",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Renew an existing custom domain registration using organization credits, extending its expiration date with upstream registries. Mutates organization credit balance. Requires domain and confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Input documentation gives an agent enough context to populate the arguments.
domain
Custom domain name to route to the project (e.g. app.example.com).
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
List user and system notifications, returning notification IDs, alert titles, message contents, notification categories (deployment, domain, security, billing), read/unread status, and timestamps.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
List chronological team activity feed across projects and resources, returning event IDs, action types, actor user details, affected resource targets, and event timestamps.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
List security and compliance audit log entries, returning timestamped records of administrative actions, permission changes, authentication events, API token usages, and IP addresses.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
List all organizations of which the authenticated user is a member, returning organization IDs, organization names, URL slugs, subscription tiers, and user role assignments.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Retrieve organization resource limits and current usage, returning max allowed projects, active deployments, member seats, database limits, CPU/memory quotas, and consumed allocations.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
List customer support tickets submitted by the organization, returning ticket IDs, subjects, descriptions, priority levels (low, medium, high, urgent), resolution status, and staff replies.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Perform a rolling restart of all active runtime containers for a project without rebuilding images. Mutates running container processes to apply fresh configurations or clear memory leaks. Requires projectId and confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs80/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_restart_runtime",
"title": "Restart Runtime",
"description": "Perform a rolling restart of all active runtime containers for a project without rebuilding images. Mutates running container processes to apply fresh configurations or clear memory leaks. Requires projectId and confirmed: true.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Project to operate on; use the project identifier as id in place of projectId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Confirmation of execution; when omitted or false, destructive actions are blocked without making changes."
},
"projectId": {
"type": "string",
"minLength": 1,
"description": "Project identifier obtained from deployxa_list_projects or deployxa_create_project."
}
}
},
"annotations": {
"title": "Restart Runtime",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Retrieve container autoscaling policies for a project, returning minimum replica counts, maximum replica limits, CPU/memory scaling thresholds, and current replica numbers.
The description explains the capability, when to use it, and what to expect.
Inputs73/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Execute the standard automated deployment workflow for a project, pulling latest Git commits, running builds, provisioning containers, and updating routing. Mutates project deployment state. Requires projectId and confirmed: true.
Resolve contradictions between the description, input schema, and annotations.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Request a rollback using a successful deployment in the organization, subject to workload policy. First attempts to restore the warm standby release; otherwise queues a deployment using the requested deployment's existing image without rebuilding it. Changes production routing and workloads. Returns the instant rollback result or the queued deployment; confirmation is optional under the tool policy.
Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
deploymentId
Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment.
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_rollback_workflow",
"title": "Trigger Rollback Workflow",
"description": "Request a rollback using a successful deployment in the organization, subject to workload policy. First attempts to restore the warm standby release; otherwise queues a deployment using the requested deployment's existing image without rebuilding it. Changes production routing and workloads. Returns the instant rollback result or the queued deployment; confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Deployment to inspect or operate on; use the deployment identifier as id in place of deploymentId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"deploymentId": {
"type": "string",
"minLength": 1,
"description": "Deployment identifier obtained from deployxa_list_deployments or deployxa_create_deployment."
}
}
},
"annotations": {
"title": "Trigger Rollback Workflow",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Retrieve billing cycle resource usage for a project, returning compute runtime hours, memory consumption, disk storage, data transfer egress bandwidth in bytes, and estimated charges.
The description explains the capability, when to use it, and what to expect.
Inputs76/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
List billing invoices and payment receipts for a project, returning invoice IDs, billed amounts, currencies, payment statuses (paid, pending, failed), invoice dates, and download links.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Resolve the mismatch between this description and its schema constraints.
projectId
Project identifier obtained from deployxa_list_projects or deployxa_create_project.
Clear enough to supply this argument.
id
Project to operate on; use the project identifier as id in place of projectId.
Resolve the mismatch between this description and its schema constraints.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Disconnect and revoke the integrated third-party Git provider. Mutates organization repository configuration by removing OAuth tokens and disabling webhook triggers. Automated deployments on git push will stop. Requires confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
Input documentation gives an agent enough context to populate the arguments.
confirmed
Authorization to remove Git provider access tokens and stop commit webhooks; when omitted or false, the repository remains connected.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Mark a notification belonging to the authenticated user as read. Returns the updated notification record with isRead set to true. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
notificationId
Notification identifier obtained from deployxa_list_notifications.
Clear enough to supply this argument.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
Clear enough to supply this argument.
id
Notification to mark as read or delete; use its identifier as id in place of notificationId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_mark_notification_read",
"title": "Mark Notification Read",
"description": "Mark a notification belonging to the authenticated user as read. Returns the updated notification record with isRead set to true. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Notification to mark as read or delete; use its identifier as id in place of notificationId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
},
"notificationId": {
"type": "string",
"minLength": 1,
"description": "Notification identifier obtained from deployxa_list_notifications."
}
}
},
"annotations": {
"title": "Mark Notification Read",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Mark all unread notifications belonging to the authenticated user as read. Updates the user inbox in bulk and returns success and the number of changed notifications. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
confirmed
Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_mark_all_notifications_read",
"title": "Mark All Notifications Read",
"description": "Mark all unread notifications belonging to the authenticated user as read. Updates the user inbox in bulk and returns success and the number of changed notifications. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of this write request; its tool policy does not require confirmation, so omission or false does not block execution."
}
}
},
"annotations": {
"title": "Mark All Notifications Read",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Permanently delete a notification entry from the system. Mutates notification storage; deleted notifications cannot be recovered. Requires notificationId and confirmed: true.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
Resolve the mismatch between this description and its schema constraints.
notificationId
Notification identifier obtained from deployxa_list_notifications.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Notification to mark as read or delete; use its identifier as id in place of notificationId.
Resolve the mismatch between this description and its schema constraints.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_delete_notification",
"title": "Delete Notification",
"description": "Permanently delete a notification entry from the system. Mutates notification storage; deleted notifications cannot be recovered. Requires notificationId and confirmed: true.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Notification to mark as read or delete; use its identifier as id in place of notificationId."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Confirmation of execution; when omitted or false, destructive actions are blocked without making changes."
},
"notificationId": {
"type": "string",
"minLength": 1,
"description": "Notification identifier obtained from deployxa_list_notifications."
}
}
},
"annotations": {
"title": "Delete Notification",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
List team members and user roles in the organization, returning member IDs, user email addresses, display names, assigned permission roles (owner, admin, member), and invitation status.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Create a new project repository and deploy it from a selected starter template. Mutates organization state by provisioning a new project, copying template files, and triggering initial build. Requires templateId and confirmed: true.
Resolve contradictions between the description, input schema, and annotations.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
templateId
Starter template identifier obtained from deployxa_list_templates.
Clear enough to supply this argument.
confirmed
Confirmation of execution; when omitted or false, destructive actions are blocked without making changes.
Clear enough to supply this argument.
id
Target starter template identifier, accepted as an alternative parameter name to templateId.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Submit a technical support ticket for the authenticated user, saving the issue and its initial message. Sends a user notification, attempts a receipt email, and notifies configured platform administrators. Returns the created ticket with its messages. Confirmation is optional under the tool policy.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
subject
Summary headline capturing the core issue or request for technical support.
Clear enough to supply this argument.
description
Comprehensive account of observed behavior, error messages, and steps to reproduce.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
priority
Business impact severity determining triage urgency and response time objectives.
Clear enough to supply this argument.
confirmed
Acknowledgment of ticket submission; this write operation submits the ticket whether confirmation is supplied or omitted.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "deployxa_create_support_ticket",
"title": "Create Support Ticket",
"description": "Submit a technical support ticket for the authenticated user, saving the issue and its initial message. Sends a user notification, attempts a receipt email, and notifies configured platform administrators. Returns the created ticket with its messages. Confirmation is optional under the tool policy.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"subject",
"description",
"priority"
],
"properties": {
"subject": {
"type": "string",
"minLength": 1,
"description": "Summary headline capturing the core issue or request for technical support."
},
"priority": {
"enum": [
"low",
"medium",
"high",
"urgent"
],
"type": "string",
"description": "Business impact severity determining triage urgency and response time objectives."
},
"confirmed": {
"type": "boolean",
"default": false,
"description": "Acknowledgment of ticket submission; this write operation submits the ticket whether confirmation is supplied or omitted."
},
"description": {
"type": "string",
"maxLength": 10000,
"minLength": 1,
"description": "Comprehensive account of observed behavior, error messages, and steps to reproduce."
}
}
},
"annotations": {
"title": "Create Support Ticket",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
Loading score analytics…
Put your MCP to the test
A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.
01Get Current UserRetrieve the authenticated user profile, returning user ID, email, display name, avatar URL, subscription plan, email verification status, auth method, and g…
02List ProjectsList projects accessible to the organization.
03Check Domain AvailabilityQuery domain registrars to check domain name registration availability, returning purchase eligibility, registration price, annual renewal cost, and premium…
04Suggest Domain NamesGenerate creative domain name suggestions based on a search keyword, returning available domain candidates, alternative TLDs, and purchase pricing.
05List OrganizationsList all organizations of which the authenticated user is a member, returning organization IDs, organization names, URL slugs, subscription tiers, and user r…
Want to run these tasks against your MCP server with us?
How do I add Deployxa Cloud Platform to Claude, ChatGPT, or Cursor?
Add Deployxa Cloud Platform to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.deployxa.com/mcp.
Is Deployxa Cloud Platform MCP ready for ChatGPT and Claude?
As of November 11, 2026, Deployxa Cloud Platform scores 100/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is Deployxa Cloud Platform's MCP tool documentation?
As of November 11, 2026, Deployxa Cloud Platform scores 82/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 68 of 68 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to Deployxa Cloud Platform?
As of November 12, 2026, alternatives to Deployxa Cloud Platform in developer-tools on the Manufact MCP leaderboard include Speko, Manufact, AgentMail, Context, and Speko.
How can Deployxa Cloud Platform improve its MCP documentation?
deployxa_list_deployments is the lowest-scoring reviewed tool at 72/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.
Cursor
Grok Bot
Grok
Muse