MCP limitations

Know what the Cavuno MCP sandbox can and cannot do before you automate a job board workflow.

The Cavuno MCP server is a JSON-oriented proxy to the Operator API. It is intentionally not a general-purpose browser, scraper, filesystem, scheduler, or integration platform.

Sandbox boundaries

Outbound fetch is blocked inside search and execute.
execute can call only cavuno.request.
Every call starts in a fresh isolate with no persistent state.
Environment variables and the local filesystem are unavailable.
MCP cannot send multipart file uploads. Use the CLI, dashboard, or direct multipart REST API instead: POST /v1/media/upload for supported media purposes, or POST /v1/companies/{id}/logo for a company logo.
CPU and wall-clock time are bounded, so long-running workflows need an external orchestrator.

Product boundaries

An MCP client decides how prompts, approvals, retries, schedules, and other tool connections work. Cavuno does not become a native Ahrefs, Semrush, Firecrawl, ATS, or newsletter integration merely because the same agent can access both systems.

Use the right surface

Use MCP for interactive agent work, the CLI for deterministic local and CI tasks, and the REST API for application code. The MCP cookbook shows the handoff explicitly when another system is involved.