@inbin/mcp
A minimal stdio-to-HTTP proxy for Inbin's ModelContext Protocol surface. Lets stdio-only MCP clients (Claude Desktop,some Cursor builds, Zed, Cline) talk to Inbin's remote endpoint athttps://inbin.dev/api/mcp.
Install & run
Nothing to install globally. Your MCP client invokes it via npx:
{
"mcpServers": {
"inbin": {
"command": "npx",
"args": ["-y", "@inbin/mcp"],
"env": {
"INBIN_API_KEY": "ink_live_..."
}
}
}
}
Get an API key from https://inbin.dev/dashboard.
What it does
- Forwards each stdin JSON-RPC message to
https://inbin.dev/api/mcpas an HTTPS POST with your Bearer key. - Streams the response back to stdout.
- Notifications (messages with no
id) get no reply, per JSON-RPC. - Concurrent in-flight requests are supported.
Tools exposed
Every Inbin application is an MCP server. Available tools:
list_inboxes— enumerate inboxes in your applist_events— filter by inbox / status / since; paginatedsearch_events— substring search over id / subject / from / toget_event— a single event's parsed JSON + delivery historydescribe_schema— the current extraction schema
Environment
| Variable | Required | Description |
|---|---|---|
INBIN_API_KEY |
yes | your Inbin API key |
INBIN_MCP_URL |
no | override the endpoint (defaults to production) |
INBIN_MCP_DEBUG |
no | set to 1 for stderr logs |
Remote (recommended)
If your MCP client supports Streamable HTTP transport, skip thiswrapper entirely and connect directly:
{
"mcpServers": {
"inbin": {
"url": "https://inbin.dev/api/mcp",
"headers": {
"Authorization": "Bearer ink_live_..."
}
}
}
}
License
MIT.