Web Envy 360 MCP is designed to let approved AI clients discover business context, analyze customer signals, and prepare bounded actions without bypassing organizational controls.

Status and access

The MCP server is under development. There is no public production endpoint or self-service credential flow yet. Early-access deployments will be provisioned with explicit tenant, location, resource, and action scopes.

Planned resources

  • Locations: canonical business details, hours, categories, and operational metadata
  • Reputation: review summaries, response coverage, themes, and trends
  • Listings: publication status, completeness, conflicts, and recommended corrections
  • Conversations: permissioned customer-contact context and workflow state
  • Insights: aggregated performance signals and location comparisons

Draft tool surface

locations.search

Find locations by name, market, external identifier, status, or category.

reviews.summarize

Summarize approved review sets by location, date range, theme, or sentiment.

listings.audit

Return listing completeness and conflict findings for an approved location scope.

responses.prepare

Prepare a response draft using approved brand guidance; human approval remains configurable.

reports.compare

Compare approved performance measures across locations or defined cohorts.

Illustrative client configuration

{
  "mcpServers": {
    "webenvy360": {
      "url": "https://mcp.webenvy360.io/v1",
      "authorization": "OAuth 2.1",
      "status": "developer-preview"
    }
  }
}

The hostname and configuration above are reserved examples, not a currently active endpoint.

Security model

Planned controls include OAuth 2.1 authorization, tenant isolation, least-privilege scopes, location-level access boundaries, configurable write approvals, audit events, rate limits, and revocation.

Versioning

Preview documentation uses date-based revisions. Production tools will publish stable schema versions and communicate deprecations before incompatible changes.