Developer documentation

MCP client configuration

AbuseZero uses the standard protocol so compatible clients need no AbuseZero-specific model integration.

Remote clients

Choose Streamable HTTP and enter https://mcp.abusezero.com/mcp/test or /mcp. Prefer the client’s OAuth flow; use an Authorization bearer header only when the client protects secrets appropriately.

Stdio-only clients

Run the optional abusezero-mcp command included in @abusezero/sdk locally and provide the remote endpoint through its environment. The bridge forwards MCP messages and contains no separate policy or domain logic.

Compatibility boundary

AbuseZero tests the official MCP Inspector plus representative OpenAI-based, Anthropic-based, independent IDE, and independent automation clients. Compatibility means standards-compliant MCP behavior, not proprietary behavior from every client version.