Keep the clients. Centralize the controls.
Connect supported coding agents, desktop clients, and internal applications to your model and MCP gateways. Evaluate each client against the endpoints and authentication methods it supports.
Start with a supported endpoint
Clients with configurable compatible model endpoints can send requests through the model gateway. MCP-capable clients can connect to governed tool endpoints. Configure authentication and permissions for each integration.
Keep model choice separate from policy
Choose supported providers for the workflows your teams need. Model capabilities and client behavior differ, so test streaming, tool use, and authentication with your selected combination.
Know what is covered
SystemPrompt governs the requests and tool calls routed through its endpoints. Direct provider connections, local shell commands, and other paths need their own controls. Include client configuration and network policy in your deployment review.
Bring your deployment questions.
Discuss your clients, tools, and security requirements with the team building SystemPrompt.