Webvizio for AI agents
Webvizio lets teams annotate live web pages and track feedback as tasks, used by web teams collecting and managing bug reports and change requests. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Webvizio.
List tracked web projects
Pull the current projects being tracked as a read-only overview.
List webhook subscriptions
Check which webhooks are configured before adding or changing one.
Review feedback before assigning it
Look at open feedback items on a project before deciding who should address them.
2 Webvizio actions, graded by risk.
Every Webvizio action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- webvizio.list_projectsList Webvizio projects
- webvizio.list_webhooksList webhook subscriptions
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Webvizio in three steps.
- 01Your users connect WebvizioThey add their Webvizio api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Webvizio through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('webvizio', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Webvizio connects.
Users add their Webvizio api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Webvizio connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Webvizio from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore project management apps.
Webvizio and Arc0, answered.
Can I use Webvizio with Claude, ChatGPT or Cursor?
Yes. Connect Webvizio to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Webvizio actions you allow.
How do users connect Webvizio?
Users add their Webvizio api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Webvizio actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Webvizio?
Yes. Allow read actions and deny writes in the Webvizio policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Webvizio too?
Yes. The same Webvizio connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Webvizio into your agent.
Your users connect Webvizio once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan