Deploy with MCP
vastframe runs a remote MCP server (Streamable HTTP) so an AI assistant can create projects, deploy, read logs, roll back and manage data on your behalf. This page covers the deploy loop; Agents & MCP covers setup for each client and the full tool list.
The endpoint
The MCP endpoint is mcp. plus your console's domain, at /mcp: for example https://mcp.apps.contoso.com/mcp. On a local stack use http://localhost:4780/mcp or http://mcp.apps.localhost/mcp.
Prompts that work
Deploy this folder to vastframe.
Deploy this as a preview only, don't switch production.
Show me the build log for the last deploy of q3-variance.
The last deploy broke the chart. Roll q3-variance back.
Share this app with Finance - FP&A and give Priya the editor role.
What the tools do
| Step | Tool | Notes |
|---|---|---|
| Create the project | create_project | Optional: deploy creates it when missing |
| Upload and deploy | deploy | Takes files (a list of { path, content, encoding }, preferred for agents) or tarball_base64; promote (default true; false for preview only); wait_seconds (default 180, up to 600); purpose |
| Check progress | get_status | Deployments, URLs and the project's access requests |
| Read logs | get_logs | Build and runtime output |
| Switch production | promote, rollback | Same rules as the console |
deploy returns the production URL, the immutable preview URL, the tail of the build log, and any access requests it created.
Purpose and access requests
When the code uses an integration that needs approval, deploy scans the files first and requires a purpose: one line written for the approver, such as "Support leads see open escalations by account owner". Without it the tool answers with the integration and code lines it found, so the agent can ask you and retry. The app still goes live once deployed; ungranted calls answer ACCESS_PENDING until approved, and the agent can follow up with list_requests.
Tips for agents
- Exclude
node_modules,.git, build output and secrets fromfiles. - Use binary-safe
encoding: "base64"for images and other binary files. - Read the SDK docs once with
get_docs; they cover sign-in, the database, storage, integrations and error codes. - Never write login code: the Edge already signs people in.
MCP clients authenticate with a development bearer token today (Authorization: Bearer dev-token). An OAuth authorization server, so clients sign in through your identity provider and Copilot Studio can register dynamically, is coming soon.