About inbin
inbin is a stdio-to-HTTP proxy for Inbin's remote MCP endpoint, enabling stdio-only MCP clients to query parsed email events. It is for Inbin users who need to list inboxes, filter events, and retrieve structured results from their client.
Key features
- 01Forwards JSON-RPC to an HTTPS endpoint
- 02Lists inboxes and filters email events
- 03Searches events and retrieves parsed results
- 04Queries event data and describes extraction schema
- 05Supports concurrent requests
Use cases
- 01Connect to Inbin from a stdio-only client
- 02Filter events by inbox, status, or time
- 03Inspect extracted email records and delivery history
MCP support
The proxy forwards MCP clients' stdio JSON-RPC requests to Inbin's remote MCP endpoint over HTTPS and returns its responses. It lets clients without Streamable HTTP support call Inbin's email-event tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.inbin.dev/mcpclaude mcp add --transport http yaotsakpo-inbin https://api.inbin.dev/mcp{"mcpServers":{"yaotsakpo-inbin":{"type":"http","url":"https://api.inbin.dev/mcp"}}}Open in Cursor{"servers":{"yaotsakpo-inbin":{"type":"http","url":"https://api.inbin.dev/mcp"}}}Open in VS Code{"mcpServers":{"yaotsakpo-inbin":{"type":"http","url":"https://api.inbin.dev/mcp"}}}{"mcpServers":{"yaotsakpo-inbin":{"serverUrl":"https://api.inbin.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.inbin.dev/mcpAuth requiredTools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| purpose_label | string | No | Optional human-readable label for what this inbox is for. |
Details
From the project README@inbin/mcp
A minimal stdio-to-HTTP proxy for Inbin's Model
Context Protocol surface. Lets stdio-only MCP clients (Claude Desktop,
some Cursor builds, Zed, Cline) talk to Inbin's remote endpoint at
https://api.inbin.dev/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://api.inbin.dev/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 historyquery_events— filter, sort, group and aggregate over extracted records (your inbox as a table)describe_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 this wrapper entirely and connect directly:
{
"mcpServers": {
"inbin": {
"url": "https://api.inbin.dev/mcp",
"headers": {
"Authorization": "Bearer ink_live_..."
}
}
}
}
License
MIT.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.