Drive ByteVet from your AI agent
ByteVet exposes every bin operation over an OAuth-gated MCP server. Connect an agent (Claude Code, Claude.ai, Claude Desktop, or any MCP-compatible client) and it can create bins, read captured HTTP/DNS traffic, drive remote shells, and run XSS payloads — under the same quotas and ownership rules as the web dashboard.
https://byte.vet/api/mcpOAuth 2.1 + DCR
Install
Each client handles OAuth + Dynamic Client Registration automatically. Paste the snippet, then sign in with GitHub or Google when prompted.
Claude Code (CLI)
Adds the server to your local Claude Code config. First call opens a browser for sign-in.
claude mcp add --transport http bytevet https://byte.vet/api/mcpClaude (web, desktop, mobile)
On claude.ai: Settings → Connectors → Add custom connector → paste the URL. The connector is brokered through your Claude account, so it lights up on Claude Desktop and mobile automatically — no per-app config needed.
https://byte.vet/api/mcpCursor
Save as ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project. Cursor runs OAuth + Dynamic Client Registration automatically on first use.
{
"mcpServers": {
"bytevet": {
"url": "https://byte.vet/api/mcp"
}
}
}Antigravity CLI
Save as ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json in a workspace, then open /mcp in the CLI to sign in with GitHub or Google. Antigravity registers itself with ByteVet automatically. (Antigravity CLI replaced Gemini CLI in June 2026.)
{
"mcpServers": {
"bytevet": {
"serverUrl": "https://byte.vet/api/mcp"
}
}
}OpenAI Codex CLI
`codex mcp add` writes the server into ~/.codex/config.toml; `codex mcp login` registers Codex with ByteVet and opens a browser for GitHub/Google sign-in. Add `--no-browser` on a machine without a browser.
codex mcp add bytevet --url https://byte.vet/api/mcp
codex mcp login bytevetMCP Inspector
Run the Inspector locally, then in the UI pick Streamable HTTP and paste the server URL. Useful for poking at tools/list and tools/call by hand.
npx @modelcontextprotocol/inspector
# In the UI:
# Transport: Streamable HTTP
# URL: https://byte.vet/api/mcpAuth happens on first call
Your MCP client opens a browser for GitHub or Google sign-in and a one-time consent screen. It then keeps a token locally and refreshes it silently until you revoke it under Connected apps on your dashboard. Connected before 28 Oct 2026? Reconnect once — older tokens no longer work.
Authorization & revocation
Every connected MCP client appears on your dashboard under "Connected apps" with the last-used time and the source IP + location of the most recent call. Revoke it to invalidate its tokens instantly; the next call returns 401 and the client has to re-authorize.
Manage tokens in the dashboard →Troubleshooting
OAuth error: invalid_client
Your client is presenting a cached client_id that ByteVet doesn't know about — usually from a previous server. Clear OAuth credentials in your MCP client (Inspector: "Clear OAuth credentials"; Claude Code: re-run `claude mcp add`) and reconnect to trigger fresh Dynamic Client Registration.
Invalid redirect URI
The Inspector binds to a random localhost port at startup. If you registered a client and then restarted the Inspector, the new port won't match the redirect_uri you registered with. Re-register the client.
401 after long idle
Access tokens expire after an hour by default. The MCP client should refresh transparently — if it doesn't, reconnect and it will run the refresh flow.