Aurora
Server Details
Create, edit, preview, and deploy full-stack web apps to a live URL from any MCP client.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 29.4% over 41 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 17 tools
Most tools target clearly distinct resource+action pairs (read_file vs read_files differ by count, deploy vs redeploy differ by new vs existing site, start vs restart_dev_server are distinct). Minor potential confusion exists between chat (AI agent edits) and apply_changes (direct edits), but descriptions delineate them well. Overall boundaries are clear.
Strong, predictable snake_case verb_noun pattern throughout (get_project, list_projects, create_project, read_file, read_files, apply_changes, share_preview). A few bare-verb outliers (chat, deploy, redeploy) and the odd get_started deviate slightly but remain readable and don't break the convention.
17 tools is well-matched to a full-stack app platform spanning creation, coding, dev-server management, preview sharing, and deployment. Each tool earns its place, though it sits near the upper edge of the comfortable 3-15 range.
Strong lifecycle coverage of create/edit/deploy/preview/file access. However, notable gaps exist: no delete_project, no project-settings update, and no tool to set project secrets despite restart_dev_server referencing changed secrets. These omissions create some dead ends for a platform presented as full-featured.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Added
share_preview
1 tool update
- Changed
create_project1 field changed- added
Input schema / properties / filesAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional starting code, written as the project's first commit. Each item is {\"path\": \"app/routes/index.tsx\", \"content\": \"<full file>\"}. The home page is app/routes/index.tsx, components go in app/components/, and imports must be relative (all conventions: get_started)." +}
1 tool update
- Changed
apply_changes1 field changed- changed
Input schema / properties / changes / descriptionPrevious value: -"All file changes for the task. Each item is one of: {\"path\": \"src/App.tsx\", \"content\": \"<full file>\"} writes a whole file (created if missing); {\"path\": \"src/App.tsx\", \"replacements\": [{\"old\": \"...\", \"new\": \"...\"}]} edits an existing file in place; {\"path\": \"src/old.tsx\", \"delete\": true} deletes a file."New value: +"All file changes for the task. Each item is one of: {\"path\": \"app/routes/index.tsx\", \"content\": \"<full file>\"} writes a whole file (created if missing); {\"path\": \"app/routes/index.tsx\", \"replacements\": [{\"old\": \"...\", \"new\": \"...\"}]} edits an existing file in place; {\"path\": \"app/components/Old.tsx\", \"delete\": true} deletes a file."
16 tool updates
- First observed
apply_changes - First observed
chat - First observed
chat_status - First observed
create_project - First observed
deploy - First observed
get_deployment_status - First observed
get_dev_logs - First observed
get_file_tree - First observed
get_project - First observed
get_started - First observed
list_projects - First observed
read_file - First observed
read_files - First observed
redeploy - First observed
restart_dev_server - First observed
start_dev_server
Publisher details
- Operator
- Aurora Labs · Publisher source
- Operator website
- https://aurora.build
- Vendor relationship
- First-party
- Documentation
- https://docs.aurora.build
- Trust center
- Not available
- Restrictions
- Not available
Related MCP Connectors
Build, deploy, and host full-stack web apps from any MCP client. DB, auth, storage, cron included.
Build and publish full-stack apps from your coding agent: models, rules, pages, auth, per-app MCP.
Build multi-tenant apps over MCP. Schemas, CRUD, deploys — access control enforced server-side.
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets a coding agent turn a plain-language idea into a real, shareable product — creating the project and data model, serving live API endpoints, deploying custom endpoints and server-side functions, and reading request and function logs. It handles sign-up, OAuth-backed access, and OpenAPI spec generation so people can open, sign into, and use the app the agent builds.MIT
- AlicenseAqualityCmaintenanceDeploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.812 npmMIT
- AlicenseNot gradedqualityBmaintenanceDeploy GitHub repositories or local directories to private URLs directly from an MCP client. Includes tools for managing deployments, reading build logs, and stopping services.15 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to deploy full-stack web apps to Cloudflare, including databases, authentication, and file storage, directly through natural language.-
Glama MCP Gateway
Add one secure layer between your agents and this server.