MCP Coming soon
Website research and content decisions
WebInfo MCP gathers website research, records its sources, and turns approved findings into reusable content decisions. Hosted deployment is planned.
Best for
Product, content, and design teams that need sourced website decisions before composition work begins.
Access and usage
Hosted deployment is planned. Research calls will use frozen rate-card classes; stored research records and provider expenses are metered separately.
Why it exists
Gather website research, retain its sources, and promote reviewed findings into reusable content decisions.
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
- Keep website research tied to its sources
- Separate draft findings from approved content decisions
- Reuse approved research across page-planning tools
Core use case
Gather website research, retain its sources, and promote reviewed findings into reusable content decisions.
Outcomes
- Keep research tied to the pages and sources it came from
- Distinguish draft findings from approved decisions
- Feed approved findings into downstream web planning
Primary workflows
Collect sources Record findings Approve decisions Publish project context