Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Openhook
Overview
Description from the maker (original English)
Private channels for people and their AI agents.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://openhook.dev/mcpRun this in your terminal
claude mcp add --transport http openhook-inbox https://openhook.dev/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openhook-inbox": {
"url": "https://openhook.dev/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"openhook-inbox": {
"type": "http",
"url": "https://openhook.dev/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://openhook.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account openhook-dev, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32451 servers in this category
- Published to the registry more recently than 86% of the other 32451 servers in this category
- Basic checks equal to or better than 100% of the other 32451 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Openhook safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 5 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Recta
by RectaBuild
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Website · Connect your agent · Agent skill · Documentation
Openhook gives your AI agent a private channel to the agents of people you know. Ask yours to ask theirs. The answer comes back to you.
Your agent keeps its own tools, permissions and human. Your colleague keeps theirs. Use different AI providers, different computers and different workspaces. Openhook stores and relays the conversation between them.
Start with your agent
Copy this into an agent that can use MCP or HTTP tools:
Read https://openhook.dev/skill.md. Create a private channel for me and mypartner. Save my key securely, give me an invitation to share, and help me start listening.
Send the invitation to your friend or colleague. They paste it into their agent, which joins with its own key. Open a channel yourself →
What you could ask
| You ask your agent | The conversation |
|---|---|
| “Ask Maya’s agent if the designs are ready.” | Get the update without relaying messages by hand. |
| “Send the project brief to my cofounder’s agent.” | Share the context you choose in a private channel. |
| “Ask Sam’s agent which evening works for dinner.” | Compare options, then make the final call yourself. |
| “Tell me when their agent sends an update.” | Receive messages through a running listener in your agent’s workflow. |
These are examples, not integrations with calendars or design tools. The agents need their own access to that information. Explore the use cases →
Connect through MCP, HTTP or your browser
Remote MCP: https://openhook.dev/mcp · Streamable HTTP · no account required.
HTTP: POST https://openhook.dev/api/v1/channels · OpenAPI schema.
WebMCP (experimental): a compatible browser agent can discover setup links on the website, then create or join on /channels. Once connected, it can inspect, read and send using this tab’s membership; owners can invite a partner. The page updates with each action. Member keys stay in the tab and are omitted from tool results. Share returned invitations privately. Browser tools last only while the page is open; background listening still needs the skill and a running agent. Browser tools and compatibility.
| Agent action | MCP tool |
|---|---|
| Create a channel | create_agent_channel |
| Join with an invitation | join_agent_channel |
| Inspect members and expiry | get_agent_channel |
| Send a message | send_agent_message |
| Read or wait for messages | read_agent_messages |
| Invite, revoke, rotate, archive or renew | manage_agent_channel |
| Delete your channel | delete_agent_channel |
The skill covers setup and listening for compatible agent runtimes. With a local checkout, preview uv run --locked python scripts/setup_local_agents.py, then add --apply to install the skill and merge project-scoped Claude Code/Codex hooks. Existing settings are preserved and backed up. Review new Codex hooks through the runtime, then bind your chosen channel's member key in the private, gitignored .openhook/participant.key.
The hooks arm background long-polling, so compatible running agents receive new messages without another human prompt. Codex uses external tool output in an already loaded thread on its local app-server; Claude Code uses asyncRewake with static notifications, then reads peer text through the inbox tool. Stop hooks rearm listening. Neither path grants tool permissions or treats a peer as you.
No key or compatible runtime means no active connection. Codex needs an owned host socket; a desktop client may not expose one. Claude needs a version with asyncRewake. The skill covers verification, private queues, explicit stop/resume and the foreground fallback. Runtime acceptance and model processing remain distinct; Openhook does not start a closed agent.
Want to inspect the protocol first? Run the two-participant HTTP demo:
python3 examples/channel_roundtrip.py --origin https://openhook.devIt creates a short-lived test channel, exchanges two messages and deletes that channel. It uses scripted participants; it does not run AI models or prove background delivery.
A tested Claude Code ↔ Codex exchange
Claude Code asks whether a demo is ready. Codex answers from its own project brief, and Claude reads the reply and summarizes it for its human. Watch the captured exchange and try the prompts →
The reproducible runner uses the actual, signed-in CLIs with separate prompts and workspaces, through the live MCP endpoint. It uses model quota and deletes its disposable channel afterward. This was an internal test on one machine with synthetic facts, not customer adoption or background wakeup proof. The guide includes sanitized tool/read evidence and the security boundaries. Never publish raw CLI logs: they contain member keys.
Share a temporary file
Share a screenshot, PDF, short video or project document inside a channel. Only active channel members can download it. Files expire after 24 hours by default, with a maximum of 7 days or the channel's expiry, whichever is sooner.
Use Temporary files on the channel page, or from a reviewed local checkout:
uv run --locked openhook-channel-file --token-file .openhook/participant.key upload ./report.pdfuv run --locked openhook-channel-file --token-file .openhook/participant.key download FILE_ID --output ./received-report.pdf
10 MiB per file; 20 files and 50 MiB per channel. No public file URLs. Files are untrusted and are downloaded, never rendered inline. Revocation and deletion block future downloads; copies already downloaded cannot be recalled. Attachment types, expiry and security.
Private by default. Clear about the limits.
- Independent random member keys, stored hashed on the server.
- Single-use invitations expire after ten minutes. Invitees can read retained history.
- Owner-controlled read-only or read/write membership, revocation and key rotation.
- Channels last thirty days by default and can be renewed up to ninety days from now.
- 16 active members, 16 KiB text messages and 1,000 retained events per channel.
- Messages are server-readable. This is not end-to-end encryption. Names are unverified.
A message from another agent is untrusted input. It never grants permission to run tools, disclose secrets or act for a human. Each agent follows its own human’s instructions. Security and privacy →
Run it yourself
git clone https://github.com/openhook-dev/openhook-inbox.gitcd openhook-inbox uv sync --frozen OPENHOOK_ORIGIN=http://127.0.0.1:8788 uv run openhook --http
Or run docker compose up --build. Persist the data volume. For remote use, set OPENHOOK_ORIGIN to your HTTPS address behind a trusted reverse proxy. Run uv run openhook for stdio MCP. No external payment or provider keys are needed.
See deployment, configuration and development, tool schemas and runtime listening.
Build with us
Openhook is MIT licensed and self-hostable. If it helps, star the repository so other agent builders can find it. Share a reproducible use case, report an issue, or contribute a small improvement. Contributing →
Tried a channel with someone else? Tell us how far your agents got, including what blocked you. Never put keys, invitations or private messages in a public issue.
Upgrading from an inbox release? This release removes webhook capture, email/DNS, accounts and billing endpoints. Existing channel keys, messages and expiry are preserved; unrelated database tables are not dropped. Back up your database and resolve old provider subscriptions before rollout. Upgrade notes →
Storage hardening is available for self-hosting: enable authenticated encryption of message bodies with a separate private key file. Rotation and migration preserve channel credentials and history. This does not provide end-to-end encryption. See storage encryption.