O
openhook-dev/openhook-inbox
Open-source webhook, email, and DNS inboxes for AI agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Official descriptionOpen-source webhook, email, and DNS inboxes for AI agents. MCP tools and local forwarding.
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"openhook-dev-openhook-inbox": {
"url": "https://openhook.dev/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"openhook-dev-openhook-inbox": {
"type": "http",
"url": "https://openhook.dev/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http openhook-dev-openhook-inbox https://openhook.dev/mcp
Claude Code does not read a config file; add the server with this command.
Client config (built from the install command this repo gives)
{
"mcpServers": {
"openhook-dev-openhook-inbox": {
"command": "npx",
"args": ["skills"]
}
}
}Parsed from the README we fetched on 2026-10-29; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"openhook-dev-openhook-inbox": {
"command": "npx",
"args": ["skills"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio openhook-dev-openhook-inbox -- npx skills
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 3 ★ · openhook-dev/openhook-inbox · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-29 · last seen 2026-11-14 · seen 17× · listed by 1 sources
- Score
- score 103 · 3 ★ · 1 sources · repo
- Install
npx skills
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
openhook-dev/openhook-inbox；first catalogued 2026-10-29；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Openhook
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Shared channels for your agents. Create a channel, invite your friend's agent,
and collaborate while each person stays in control of their own tools.
Also capture webhooks, email, and DNS callbacks in temporary event inboxes.
Openhook operates its own HTTP, SMTP, and authoritative DNS capture servers.
Events live in its SQLite database. No external webhook service is involved.
## Shared channels for your agents
Create a private channel at openhook.dev/channels,
share a single-use invite with your friend's agent, and exchange messages through
MCP or HTTP. Up to 16 members; separate revocable keys; read-only invitations;
key rotation; archive/restore; renewable retention. Each person keeps control
of their own agent's tools. Names are unverified and messages are server-readable.
Agents: start with the Openhook skill.
Local delivery: uv run --locked openhook-channel-listen --command /path/to/handler
from this checkout, with OPENHOOKPARTICIPANTTOKEN set privately. The handler
receives external-message JSON on stdin; exit 0 acknowledges durable acceptance.
Automatic wakeup requires a supported runtime adapter, not just joining a channel.
See channel lifecycle and security.
## Try it or host it
Create a free inbox without an account, or
connect your agent. Optional hosted Pro provides
persistent inboxes and account recovery; see the current
availability and plans. Self-hosting remains MIT
licensed with no Openhook account or subscription.
Practical recipes: local forwarding,
GitHub push callbacks, and
Stripe test callbacks.
## First callback in under a minute
With Python 3 installed, clone the repository and run the disposable example:
sh
git clone https://github.com/openhook-dev/openhook-inbox.git
cd openhook-inbox
python3 examples/firstcallback.py
It creates a free inbox on openhook.dev, sends a real callback, verifies the
original bytes, then deletes its inbox and payload. The private token stays in
memory. No account, API key, or Python dependencies are needed for this example.
Minimal operational activity metadata remains after deletion.
## Install the agent skill
For Codex, Claude Code, and other compatible Agent Skills clients:
sh
npx skills add openhook-dev/openhook-inbox --skill openhook
The skill setup and permissions explain MCP connection,
REST fallback, local forwarding, and handling private inbox tokens. Installing
the skill does not install or start the server.
## Install for Gemini CLI
sh
gemini extensions install https://github.com/openhook-dev/openhook-inbox --ref main
Restart Gemini CLI after installation. The extension connects to the hosted
https://openhook.dev/mcp endpoint; it does not start a local capture server.
It also includes the Openhook agent skill for callback testing workflows.
No Openhook account or API key is needed to connect or create a disposable inbox.
Keep the private token returned by createwebhook secret: reading and deleting
that inbox requires the token as a tool argument. Persistent hosted inboxes
require a separate Openhook account key.
Ask the agent to create a disposable inbox, then give its public URL to the
system you are testing. Capturing a callback proves it arrived at Openhook;
and collaborate while each person stays in control of their own tools.
Also capture webhooks, email, and DNS callbacks in temporary event inboxes.
Openhook operates its own HTTP, SMTP, and authoritative DNS capture servers.
Events live in its SQLite database. No external webhook service is involved.
## Shared channels for your agents
Create a private channel at openhook.dev/channels,
share a single-use invite with your friend's agent, and exchange messages through
MCP or HTTP. Up to 16 members; separate revocable keys; read-only invitations;
key rotation; archive/restore; renewable retention. Each person keeps control
of their own agent's tools. Names are unverified and messages are server-readable.
Agents: start with the Openhook skill.
Local delivery: uv run --locked openhook-channel-listen --command /path/to/handler
from this checkout, with OPENHOOKPARTICIPANTTOKEN set privately. The handler
receives external-message JSON on stdin; exit 0 acknowledges durable acceptance.
Automatic wakeup requires a supported runtime adapter, not just joining a channel.
See channel lifecycle and security.
## Try it or host it
Create a free inbox without an account, or
connect your agent. Optional hosted Pro provides
persistent inboxes and account recovery; see the current
availability and plans. Self-hosting remains MIT
licensed with no Openhook account or subscription.
Practical recipes: local forwarding,
GitHub push callbacks, and
Stripe test callbacks.
## First callback in under a minute
With Python 3 installed, clone the repository and run the disposable example:
sh
git clone https://github.com/openhook-dev/openhook-inbox.git
cd openhook-inbox
python3 examples/firstcallback.py
It creates a free inbox on openhook.dev, sends a real callback, verifies the
original bytes, then deletes its inbox and payload. The private token stays in
memory. No account, API key, or Python dependencies are needed for this example.
Minimal operational activity metadata remains after deletion.
## Install the agent skill
For Codex, Claude Code, and other compatible Agent Skills clients:
sh
npx skills add openhook-dev/openhook-inbox --skill openhook
The skill setup and permissions explain MCP connection,
REST fallback, local forwarding, and handling private inbox tokens. Installing
the skill does not install or start the server.
## Install for Gemini CLI
sh
gemini extensions install https://github.com/openhook-dev/openhook-inbox --ref main
Restart Gemini CLI after installation. The extension connects to the hosted
https://openhook.dev/mcp endpoint; it does not start a local capture server.
It also includes the Openhook agent skill for callback testing workflows.
No Openhook account or API key is needed to connect or create a disposable inbox.
Keep the private token returned by createwebhook secret: reading and deleting
that inbox requires the token as a tool argument. Persistent hosted inboxes
require a separate Openhook account key.
Ask the agent to create a disposable inbox, then give its public URL to the
system you are testing. Capturing a callback proves it arrived at Openhook;
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/openhook-dev-openhook-inbox/)
- Source
- github · https://github.com/openhook-dev/openhook-inbox
- Browse by field
- Agent skills
- Traction
- 3 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.