Aweb MCP

Aweb MCP exposes a governed meta-tool surface over Aweb capabilities and external MCP Warehouse providers. It is not a flat dump of every vendor tool. Agents discover, plan, and invoke through policy-aware entry points, backed by 62 MCP Warehouse providers and 506 MCP tools in the current catalog.

Discovery

Manifesthttps://aweblabs.ai/.well-known/mcp.json

Server transporthttps://aweblabs.ai/api/mcp

Protocol2025-11-25

Supported versions2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07

Google-managed MCP

Aweb verifies 52 official Google-managed MCP servers from Google's supported-products source. The current MCP Warehouse runtime exposes 34 governed L0/L1 Google read-only slices and keeps 18 official entries catalog-only until schema discovery, risk mapping, and policy tests are complete.

Open Google MCP catalog

Meta-tool surface

aweb_exploreDiscover Aweb capability domains and public capability metadata.

aweb_executeExecute approved Aweb capabilities through the governed meta-tool surface.

aweb_planEstimate work, cost, risk, and execution shape before invoking capabilities.

aweb_observabilityInspect Aweb runtime and warehouse observability summaries.

mcp_exploreSearch external MCP Warehouse providers and tool schemas.

mcp_invokeInvoke approved external MCP provider tools through the warehouse boundary.

mcp_subscribeSubscribe to supported provider events where a genome declares bidirectional support.

Provider genome to MCP tool mapping

MCP provider docs should be generated from the integration catalog and MCP Warehouse genomes. Each provider carries domain tags, auth mode, tool definitions, setup notes, approval notes, and risk/cost annotations where present.

curl "https://aweblabs.ai/api/v2/integrations/catalog" \
  | jq '.providers[] | select(.warehouseSources[] == "mcp_warehouse") | {
      id: .providerId,
      name: .displayName,
      tools: (.mcpTools | length),
      readiness: .readiness,
      auth: .connectionMethod
    }'

Current MCP providers

DiscordComms / ready / api_key8 tools

EtsyCommerce / ready / oauth3 tools

GEX EngineFinancial Data / ready / internal72 tools

GitHubCodehost / ready / oauth11 tools

Gmail (Google Workspace)Outreach / ready / oauth6 tools

Google DriveCommunication / ready / oauth4 tools

GumroadCommerce / ready / oauth3 tools

NeonDatabases / ready / api_key35 tools

NotionDocs / ready / oauth19 tools

PerplexitySearch / ready / api_key1 tools

PostHogAnalytics / ready / api_key2 tools

SentryObservability / ready / oauth17 tools

Safety and policy

Tool execution requires authenticated MCP access.
External provider credentials are not exposed in public docs or discovery files.
Approval-required tools are routed through OS9/Mission Contract boundaries.
Agents should call plan/discovery tools before executing mutable or high-cost actions.
Private beta providers and internal Aweb systems require explicit access.

Example agent flow

1. Fetch https://aweblabs.ai/.well-known/mcp.json
2. Authenticate against the Aweb MCP server.
3. Call aweb_explore or mcp_explore to discover capability/tool candidates.
4. Call aweb_plan for high-cost or mutable work.
5. Execute through aweb_execute or mcp_invoke.
6. Persist returned receipts, request IDs, and policy outcomes.

Access boundary

MCP execution is private beta unless your Aweb workspace has been approved. Public pages may document the architecture, manifest, and discovery shape, but must not publish secrets, internal credentials, or unstable provider operations. Start with the public API and use MCP access for approved agent/tool workflows.