Skip to main content
Simplified Webhooks exposes a remote Model Context Protocol (MCP) server, so AI agents can manage your webhooks, track record and storage usage, and — most usefully — keep an audit log of the changes an agent makes to your Airtable data. The intended setup is two MCP servers side by side: the Airtable MCP (to read and mutate records) and the Simplified Webhooks MCP (to log what changed, as a safety net). The agent enables monitoring at the start of a session, does its work through the Airtable MCP, and reviews the logged changes afterward.
This is an audit layer, not a hard guardrail. Simplified Webhooks records what changed; it does not sit in front of Airtable and block writes. Use it to review — and, if needed, manually reverse — an agent’s changes.

​
Endpoint

The server speaks streamable HTTP. Add it as a remote MCP server in any client that supports them.

​
Authentication

You can connect in two ways:

OAuth (recommended)

Clients that support OAuth (Claude, Cursor) discover the sign-in flow automatically. You approve access once on a consent screen and can revoke it anytime under Connected apps in your profile settings.

API key

For headless or CI agents, send a Simplified Webhooks API key as a bearer token: Authorization: Bearer sk_.... Create keys in your profile settings.
Either way, the agent acts as you and can only see your own data. Connect your Airtable account first (via OAuth or a personal access token) in the dashboard — the MCP tools use that same connection.

​
Adding the server

In Claude, open Settings → Connectors → Add custom connector, then paste the endpoint URL. Claude walks you through the OAuth consent screen. Once connected, the Simplified Webhooks tools appear in your conversations.

​
What the agent can do

The tools mirror the public API one-to-one.

​
The monitoring workflow

Pair the Simplified Webhooks MCP with the Airtable MCP so an agent’s edits are logged:
  1. Check permissions — get_monitoring_auth_status. Enabling monitoring creates a Monitoring Base in your Airtable account, which needs write access. If hasWriteScopes is false, grant write access in the dashboard under Change monitoring.
  2. Enable monitoring — enable_monitoring with your baseId and workspaceId. When it returns successfully, changes are captured from that moment on.
  3. Do the work — let the agent read and mutate records through the Airtable MCP as usual.
  4. Review — list_recent_changes returns what changed, newest first, filterable by event type, table, record, source, user, and date range. Each entry captures the previous values, so you can see — and manually undo — exactly what happened.
Ask the agent to enable monitoring before it starts editing, then to summarize list_recent_changes when it finishes. That gives you a reviewable record of the session.

​
Current limitations

  • No one-click revert (yet). Previous values are captured, but reversing a change is manual today.
  • Account-level access. An OAuth grant or API key gives an agent access to your whole Simplified Webhooks account; there are no per-tool permission scopes yet.
  • Monitoring is a log, not a lock. It records changes; it does not prevent them.