Otterkit
io.github.useotterkitPublished by GitHub account useotterkitv0.12.2Updated Oct 24, 2026
Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.
Overview
OtterKit exposes tunnels and webhook tooling to AI agents: capture, await, verify, replay and send signed test webhook events.
- What you can do
- Capture and inspect incoming webhook deliveries through tunnels and serverless endpoints
- Await deliveries and replay captured events to local code, optionally re-signed with a current timestamp
- Verify captured requests against a signing secret and report the failure reason
- Send synthetic provider events signed with real signature headers, such as Stripe or GitHub events
- Manage tunnels, webhook endpoints and daemons, and consult pricing information
- When to use it
- Useful when developing or debugging webhook integrations locally, for example Stripe, GitHub, Shopify or Slack handlers, and you want an assistant to capture deliveries, check signatures, or replay and synthesize events without touching the real provider.
- Requirements
- Runs as a local process over stdio, started with npx from the otterkit npm package, so Node.js is needed. Desktop only; no web executable. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Otterkit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
OtterKit Agent Skills
Skills that teach AI coding agents (Claude Code, Cursor, Copilot — anything that reads the Agent Skills format) to drive OtterKit: tunnels and serverless webhook endpoints with capture, signature verification, and replay.
Install (Claude Code)
Copy any skill directory into .claude/skills/ in your project (or ~/.claude/skills/
for all projects):
Or add the OtterKit MCP server, which exposes the same capabilities as tools:
What's different from a plain tunnel
Every skill leans on three things ngrok-class tools don't do:
otterkit send— synthetic provider events signed with real signature headers (stripe:payment_intent.succeeded,github:pull_request.opened, …) against a local handler, free, no provider account interaction.otterkit verify— check captured deliveries against a signing secret, per request, with the failure reason.otterkit replay --resign— re-deliver a captured event to local code, re-signed with a current timestamp so timestamp-tolerant handlers (Stripe, Slack) still accept it.
Skills are generated from the CLI's actual implementation and updated alongside it.
Source: README.md at commit 2ec097d
Tools
0Version history
1- v0.12.2LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.