Total requests ↗
—All recorded requestsSecurity overview
Monitor gateway activity and policy enforcement.
Secure Chat ↗Connecting
Complete your gateway setup
Check database readiness, create a client key, and configure a destination MCP server.
Violations blocked ◇
—Awaiting traffic dataRequests redacted ◌
—Allowed after policy matchingAverage latency ◷
—Gateway decision / upstream headersTraffic & violations
Daily gateway activity over the last 30 days · UTC
Requests Blocked
No traffic recorded yet. Connect an MCP client to start monitoring.
Policy signals
Most frequent matching policy combinations
Active traffic sources
Clients with the most recorded requests
Recent security alerts
Blocked events in the latest 100 requests
Control what leaves your edge
Custom rules scan requests before mandatory built-in protections.
5 built-in protections Always active
Built-in rules scan after custom policies. They cannot be disabled here.
IDENTITY & ACCESS
0 active keysOne key for each client
Provision credentials with an expiry and request budget. Revoke access independently.
Client keys
Secrets are shown once. Only SHA-256 hashes are stored.
Advanced · Source IP overrides
Manage client access
Allow or deny clients by their Cloudflare-reported source IP.
◎
Shared networks share a policy
These are IP access policies, not individual user accounts. Unlisted source IPs with a valid client credential are allowed.
Client policies
Audit event stream
Review decisions and inspect retained payloads.
Search and filters run across the database. Older pages remain loaded during refresh.
TEST BEFORE YOU ENFORCE
No upstream calls · No audit writesSee how the gateway decides
Run a synthetic JSON payload through all enabled custom rules and built-in protections.
Decision trace
Awaiting testEvaluated payload
Run a test to see the payload after policy evaluation.
A blocked decision prevents forwarding, even if other rules redact text.
CLIENT ONBOARDING
Connect through your security boundary
Create a client key, configure the endpoint, and verify the first event.
Create a client identity
Give each client its own key, expiry, and request limit. Save the generated key once.
Add a destination server
Add a server in Destinations and assign the client key or set a workspace default. This gateway does not provide upstream tools itself.
Connect and verify
Use the configuration below, reload your client, then review its requests in Audit logs.
Connection configuration
Replace YOUR_CLIENT_KEY locally. These examples contain no real credentials. Use a client key, never the admin key.
Transport and web-client compatibility
The gateway forwards POST-based MCP requests. A real upstream must complete MCP initialization and advertise tools. Separate GET event channels and OAuth discovery are not implemented. ChatGPT web’s authenticated custom MCP flow requires OAuth support beyond this shared/individual key setup.
UPSTREAM ROUTING
Your MCP server catalog
Assign a server per client key, or set a workspace default. Every request still runs through DLP.
Routing order
Client assignment → workspace default → UPSTREAM_MCP_URL environment fallback. A disabled assigned server or missing authentication Secret stops forwarding. Requests never silently switch to another server.
SECURE CHAT · MODEL ACCESS
Open Secure Chat ↗Connect AI providers
Messages are inspected before a model API is called. Model providers are separate from MCP tool destinations.
Separate user access
Set CHAT_ACCESS_KEY as a Worker Secret for chat-only users. Never share ADMIN_API_KEY with them. Signed-in administrators can open /chat directly.
Secure Chat events
Metadata only · No prompt or reply contents
Two protection layers
Secure Chat masks built-in personal and financial matches with user approval. Secrets, private keys, passwords, and custom Block rules remain blocked. The MCP gateway retains its existing enforcement behavior.
Deployment readiness
Check the services required by the management console.
Checks have not run.
Access model
- Administrator
- Shared ADMIN_API_KEY with full management access
- MCP clients
- Individual hashed keys with expiry and rate limits; shared GATEWAY_API_KEY remains supported
- Sessions
- Signed HttpOnly session cookie · Up to 8 hours · Sign out to clear it
Individual admin accounts and roles are not configured. Use your organization’s access controls for identity and MFA.
Gateway connection
CheckingPOST JSON with your gateway bearer key. The upstream must support the same request format.
Manage multiple upstreams in Destinations. UPSTREAM_MCP_URL in Cloudflare Worker Settings remains the environment fallback. This gateway URL cannot also be its destination.
How traffic flows
01MCP clientClaude or another client
02This gatewayAuthentication + DLP
03Destination MCP serverYour separate tools service
A destination MCP server provides tools or data. A standard AI chat API requires a protocol adapter; it is not an interchangeable MCP endpoint.