Webanto MCP server

Webanto's official MCP server connects AI assistants to your Webanto workspace for ecommerce catalog and SEO work. Sign in with OAuth, pick an organization, and approve scopes. Assistants can search your synced store products, read SEO health and job status, query your organization's knowledge, and queue AI product enrichment. Enrichment writes reviewable proposals only; nothing is published to a live store from MCP. Usage is metered against your plan and every connection can be revoked under Settings → API keys → Connected apps.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Webanto

MCP endpoint (Streamable HTTP)

https://api.webanto.com/api/v1/mcp

Vendor documentation

What you can do with it

Find products in a synced Shopify or WooCommerce catalog and review their copy
Check SEO health and see which products need titles, descriptions, or alt text
Queue AI enrichment for a product and track the job until the proposal is ready
Answer questions from your organization's stored brand and product knowledge

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http webanto https://api.webanto.com/api/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add webanto --url https://api.webanto.com/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable webanto in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "webanto": {
      "url": "https://api.webanto.com/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "webanto": {
      "type": "streamableHttp",
      "url": "https://api.webanto.com/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start webanto and inspect its tools.

VS Code configuration

{
  "servers": {
    "webanto": {
      "type": "http",
      "url": "https://api.webanto.com/api/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http webanto https://api.webanto.com/api/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "webanto": {
      "url": "https://api.webanto.com/api/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "webanto": {
      "serverUrl": "https://api.webanto.com/api/v1/mcp"
    }
  }
}

See all 353

Do you run Webanto?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing