MCP Coming soon
Dashboard specifications from approved web plans
WebDashboard MCP turns approved site specifications into dashboard-specific structure, states, and implementation guidance. Hosted deployment is planned.
Best for
Product teams that need a clear dashboard specification before implementation starts.
Access and usage
Hosted deployment is planned. Planning calls will use frozen rate-card classes; project artifacts will use the separate file-storage meter.
Why it exists
Turn approved site specifications into dashboard hierarchy, component states, responsive behavior, and implementation guidance.
Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.
Connection and contract
The intended MCP contract is documented for evaluation, but no public hosted endpoint is available yet.
The product-specific schema defines the inputs and outputs used by clients and downstream automation.
Current limits
The page describes planned product scope. Tool availability, runtime behavior, and performance should not be inferred before the production gate passes.
What you get
- Define dashboard information hierarchy and states
- Reuse approved site contracts and design constraints
- Prepare implementation guidance without mutating a repository
Core use case
Turn approved site specifications into dashboard hierarchy, component states, responsive behavior, and implementation guidance.
Outcomes
- Define dashboard structure before code changes begin
- Cover loading, empty, error, and populated states
- Keep dashboard decisions tied to the approved site contract
Primary workflows
Load contract Define hierarchy Specify states Prepare implementation