Newsletter
Stay Ahead
Occasional, engineering-led notes on applied AI — what we're building, running, and learning in production.
Occasional, engineering-led notes on applied AI — what we're building, running, and learning in production.
Ask your AI assistant about your store catalog, queue product copy for review and find Search Console opportunities. You sign in with your Webanto account and choose exactly what it can see.
Server URL
https://api.webanto.com/api/v1/mcpAdd the server URL to any client that supports remote MCP servers. Clients that support OAuth open a Webanto sign-in window the first time you use it.
In Claude, open Settings → Connectors, choose Add custom connector, and paste this URL.
https://api.webanto.com/api/v1/mcpIn ChatGPT, turn on developer mode under Settings → Apps & Connectors → Advanced, then create a connector with this URL.
https://api.webanto.com/api/v1/mcpRun this in your terminal. Inside Claude Code, run /mcp to sign in.
claude mcp add --transport http webanto https://api.webanto.com/api/v1/mcpRun this in your terminal. Codex opens the Webanto sign-in the first time it connects.
codex mcp add webanto --url https://api.webanto.com/api/v1/mcpAdd this to your project's Cursor MCP file, then sign in from Cursor's MCP settings.
.cursor/mcp.json
{
"mcpServers": {
"webanto": {
"url": "https://api.webanto.com/api/v1/mcp"
}
}
}Add this to your workspace MCP file, then start the server from the file to sign in.
.vscode/mcp.json
{
"servers": {
"webanto": {
"type": "http",
"url": "https://api.webanto.com/api/v1/mcp"
}
}
}Webanto uses standard OAuth 2.1. Your assistant never sees your password, and you can disconnect it at any time.
Step 1
Paste the server URL into your assistant. It registers itself with Webanto automatically.
Step 2
A Webanto window opens. Sign in and choose which organization the assistant works with.
Step 3
Untick anything you don't want to share. The assistant only sees the tools you approve.
Step 4
Every connection is listed under Settings → API keys → Connected apps, where one click revokes it.
Each tool needs a permission you grant at sign-in, and the person who connected it must still hold the matching role in the organization.
webanto_list_products
Search and filter connected-store products
webanto_get_product
Read one connected product with its proposed copy
webanto_list_copy_proposals
Read the copy review queue and its counts
webanto_enrich_product
Queue AI-generated product copy as a proposal
webanto_get_job
Read a job created by this connection
webanto_search_console_opportunities
Read Search Console page and product opportunities
webanto_search_memory
Search the organization's knowledge base
Access is limited to one organization and the permissions you ticked. Asking for more needs your approval again.
Access tokens expire after an hour. Disconnecting an app ends its access straight away.
AI work uses your organization's credits and rate limits, exactly like an API key.
Generated copy waits in your review queue. No tool publishes to a live store.
Clients without OAuth can send a Webanto API key instead. Create a key with the scopes you need and pass it as a bearer token.
{
"mcpServers": {
"webanto": {
"type": "http",
"url": "https://api.webanto.com/api/v1/mcp",
"headers": { "Authorization": "Bearer ${WEBANTO_API_KEY}" }
}
}
}