Your Coding Agent, On the Record

Every tool call logged. Your rules on every call.

Add ContextGate to Claude Code, Cursor, VS Code or Codex as one MCP server. Every tool call through it is logged, checked against your policies, and blocked, warned on or redacted when it should be. Free.

$claude mcp add --transport http contextgate https://api.contextgate.ai/mcp

Then sign in to ContextGate when your app asks (in Claude Code, run /mcp). New to ContextGate? Signing in creates your free account. Setup in ContextGate walks you through Codex, Gemini CLI, Claude and ChatGPT too.

ContextGate
Checks and logs every tool call
⌨️
Claude Code
Terminal
✏️
Cursor
Editor
🧩
VS Code
Editor
🖥️
Claude Desktop
App
🤖
Your own agent
API key
🐙
GitHub
App
💬
Slack
App
✉️
Gmail
App
🔌
Your MCP server
Remote MCP
Your AI apps
⌨️
Claude Code
Terminal
✏️
Cursor
Editor
🧩
VS Code
Editor
🖥️
Claude Desktop
App
🤖
Your own agent
API key
↕
ContextGate
Checks and logs every tool call
↕
Connected apps
🐙
GitHub
App
💬
Slack
App
✉️
Gmail
App
🔌
Your MCP server
Remote MCP
⌨️

One command

The installer signs you in through your browser, finds Claude Code, Claude Desktop, Cursor and VS Code on your machine, and adds ContextGate to the ones you pick.

🛡️

Every call checked

Each tool call is checked against your workspace policies, then logged with its arguments, the redacted result and what your policies decided.

🔌

Only the tools you want

Switch off individual tools on a connection. Switched-off tools are hidden from your AI app and refused if called.

Connections

One Place for Every Connection

Add apps such as Gmail, GitHub, Salesforce and HubSpot from the app catalog, or any remote MCP server. Switch off the tools you don't want used: they're hidden from your AI apps and refused if called.

Health monitoring
Each connection shows its health and flags when it needs re-authentication
Tool sync
Tool lists sync from each app and MCP server
Switch tools off
Hidden from your AI apps and refused if called
Any remote MCP server
Add your own servers alongside catalog apps

MCP Tools Are Powerful. Unchecked, They're Risky.

No Record
Your coding agent calls MCP tools for you. There's no shared record of which tool it called, with what arguments, or what came back.
Data and Secrets in the Call
Tool results hand personal data straight to the model. API keys get pasted into tool arguments.
Every Tool, Every Time
Connect an MCP server and every tool on it is in reach: merge, delete, send, write. Not just the few you meant the agent to use.
How it works

One Connection. Every Call Checked.

It takes minutes, and you keep working in the AI app you already use.

1

Add ContextGate

One command in Claude Code, or one click in Cursor or VS Code. Sign in when your app asks; that creates your free account if you don't have one.

$ claude mcp add --transport http contextgate https://api.contextgate.ai/mcp
2

Connect

Add apps such as GitHub, Slack and Gmail from the app catalog, or any remote MCP server, including your own. Tool lists sync from each one.

3

Set your rules

Switch off tools you don't want used. Add policies: plain-English governance checks, PII redaction, secrets blocking and blocked patterns.

4

Work

Keep using your AI app. Every tool call through ContextGate is logged and checked, then allowed, warned on, redacted or blocked.

Other AI apps

$ codex mcp add contextgate --url https://api.contextgate.ai/mcp
Codex: add ContextGate, then sign in with the next command.
$ codex mcp login contextgate
Codex: sign in to ContextGate.
$ gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp
Gemini CLI: add ContextGate, then run /mcp auth contextgate to sign in.

Any other MCP client: add a remote (HTTP) MCP server with the URL https://api.contextgate.ai/mcp and sign in. A client that can't sign in can use an API key instead; Setup in ContextGate shows how.

Policies

Your Rules, On Every Tool Call

Checks run on a tool's arguments before it runs, and on its results before your AI app sees them. Each one blocks, warns or logs. Policies apply to every tool call in your workspace. Start from one of 16 templates or write your own.

🔍

PII Redaction

Personal data in tool results is replaced with placeholders before your AI app sees it. When the app sends a placeholder back, the tool gets the real value. 40 built-in types, plus your own patterns.

EmailPhoneIBANNI numberSort codeCustom patterns
🔑

Secrets & Patterns

A tool call whose arguments contain an API key, AWS key, JWT or other secret is blocked, and the secret is kept out of the log. Add your own regex and keyword patterns.

API keysAWS keysJWTsRegexKeywords
🤖

Governance Checks

Write a rule in plain English. A model that ContextGate manages judges each call against it, so you don't need model keys. Scope a check to specific tools.

BlockWarnLogArgumentsResults
Policies
Manage PII redaction and governance policies
🔒 Policy Templates
16 available
Template
Secrets & Credential Leakage
Catch API keys, tokens...
secretssecurity
2 rules · All regions
Template
Prompt Injection Defense
Block injection attempts...
securitytool-safety
3 rules · All regions
Template
GDPR Strict
Redact direct identifiers...
gdprstrict
3 rules · EU, UK
Active Policies
Engineering Guardrails
Custom · 3 rules
Active
PII redaction — Email, phone, IBAN, NI number
Secrets blocking — API keys, AWS keys, JWTs
Governance check — "Block deleting a repository or force-pushing to main"
Activity

Every Tool Call, Logged

See which AI app called which tool, for which user, with what arguments, and what your policies decided. Results are stored redacted. Filter by app, connection, tool, status, policy, user and date. Attention lists the last 7 days of blocked and warned calls in one place.

5 of 4,812
AI app

Claude

User

sarah@acme.co.uk

Connection

HubSpot

Toolbox

Default Toolbox

Policy

Client Data Protection

Rule

PII redaction

Redactions Applied
EMAIL_ADDRESS: 1UK_SORT_CODE: 1ACCOUNT_NUMBER: 1
Arguments

{ "query": "Acme Ltd" }

Result (as the AI app saw it)

{ "name": "Jo Smith", "company": "Acme Ltd", "email": "[EMAIL_ADDRESS_REDACTED_3f9a1c2e]", "note": "Refund to [UK_SORT_CODE_REDACTED_7c1e04ab] [ACCOUNT_NUMBER_REDACTED_b52d9e10]" }

ContextGate sees the tool calls that go through it. It doesn't see your AI app's built-in tools, such as Claude Code's own file edits and terminal commands, or your chats.

API keys

Your Own Agents, Same Rules

Building an agent in-house? Give it an API key and it connects to ContextGate like any other MCP client. Its tool calls are checked and logged the same way as your editor's.

Create a key

Create an API key in your workspace for an agent or script. Revoke it when you no longer need it.

Connect over MCP

Point the agent at the remote MCP URL from the Setup page and authenticate with the key.

Same policies

Your workspace policies check every tool call it makes, just as they do for your editor.

In the same log

Its tool calls appear in Activity with their arguments, redacted results and policy outcomes, next to everyone else's.

Team

One Workspace. Your Whole Team.

Invite your teammates. Their AI apps connect to the same workspace, under the same policies, and every tool call lands in the same Activity log.

🤝

Invite your team

Add teammates as Owner, Admin, Member or Viewer. Each person signs in to ContextGate from their own AI apps.

🤖

See who is connected

The Agents page lists the AI apps and API keys using ContextGate, who signed them in, and when each was first and last seen.

📊

Overview

Tool calls, blocks and warnings, calls per day by outcome, top tools and calls by AI app.

🚨

Attention

The last 7 days of blocked and warned calls in one list.

Team
Manage workspace members
colleague@company.com
Invite
EmailRole
you@company.comOWNER
sarah@company.comMEMBER
contractor@ext.ioVIEWER
Agents
AI apps and API keys using ContextGate
Claude Code
AI app · you@company.com
Last seen 2 min ago
First seen Sep 30
Cursor
AI app · sarah@company.com
Last seen 1 hr ago
First seen Oct 2
release-notes-bot
API key · you@company.com
Last seen yesterday
First seen Oct 9
API keys can be created and revoked at any time

MCP Servers Added Directly vs. Through ContextGate

Capability
Added directly
+ ContextGate
Setup
Each server added to each AI app
One server per AI app; connections live in your workspace
Record of tool calls
No shared record
Arguments, redacted result and policy outcome for every call
Personal data in results
Passed to your AI app as-is
Redacted before your AI app sees it
Secrets in arguments
Sent to the tool
Blocked and kept out of the log
Plain-English rules
None
Governance checks that block, warn or log
Switching tools off
Per AI app, where supported
Hidden from your AI apps and refused if called
In-house agents
Connects to each server itself
An API key, same policies and log
Team
Each person's own setup
One workspace with Owner, Admin, Member and Viewer roles

Set Up in Minutes

Free. No card required. Add ContextGate to Claude Code, or sign up in your browser.

$claude mcp add --transport http contextgate https://api.contextgate.ai/mcp
or sign up in your browser
Get started free