Standardized tool surface
checkCoverage, getQuote, bindAssignment, and getCertificate — plus the rest of the catalog. Typed inputs, structured outputs, MCP-compliant.
1099Policy as a Model Context Protocol server. Claude, Cursor, ChatGPT, and any MCP-compatible client can call our tools through natural language. Connect once. Your agent stays in your stack.
The same contractors, jobs, quotes, assignments, policies, certificates, and invoices your developers reach through the REST API — exposed through the MCP spec. Hosted, typed, audited.
checkCoverage, getQuote, bindAssignment, and getCertificate — plus the rest of the catalog. Typed inputs, structured outputs, MCP-compliant.
Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, Continue, Cline, Zed, and any other MCP-compatible host. One URL, every agent.
OAuth sign-in grants read-only access; write tools require a write-scoped API key. Every tool call lands in the account audit trail.
One URL. The server is hosted by 1099Policy: point your client at https://mcp.1099policy.com/mcp, approve the browser sign-in, and the tools appear in your agent. Nothing to install, no daemon to maintain.
Configuration is per-client. Add the same URL to Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, and any other MCP-compatible host.
View installation guide →The MCP server exposes the same surface as the REST API: verify coverage, quote and bind assignments, pull certificates, review contractor-provided COIs, list active policies, and pull audit trails.
Each tool ships with typed schemas and structured outputs your agent can reason over.
Browse all tools →Does our HVAC sub in PA have active WC and GL for Saturday's install? becomes a typed tool call with the right contractor, work_state, and effective_date.
If the request is ambiguous, the tool returns a structured error your agent can reason over.
Read prompt patterns →Signing in through OAuth grants read-only access: an agent you authorize in the browser can look things up but can't change anything. Tools that bind or cancel coverage require a write-scoped API key.
Every tool call lands in the account audit trail, retrievable any time with getAuditTrail.
See token management →