io.github.yaotsakpo/inbin
Query Inbin's parsed email events (newsletters, invoices, alerts) as typed JSON tools.
What can you do with io.github.yaotsakpo/inbin?
- Forwards each stdin JSON-RPC message to
https://api.inbin.dev/mcp - Streams the response back to stdout.
- Notifications (messages with no
id) get no reply, per JSON-RPC. - Concurrent in-flight requests are supported.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http inbin 'https://api.inbin.dev/mcp' --header 'Authorization: <Bearer <your-inbin-api-key>>'
{
"mcpServers": {
"inbin": {
"type": "http",
"url": "https://api.inbin.dev/mcp",
"headers": {
"Authorization": "<Bearer <your-inbin-api-key>>"
}
}
}
}
@inbin/mcpclaude mcp add inbin -e 'INBIN_API_KEY=<your inbin_api_key>' -- npx -y @inbin/mcp@0.2.0
{
"mcpServers": {
"inbin": {
"command": "npx",
"args": [
"-y",
"@inbin/mcp@0.2.0"
],
"env": {
"INBIN_API_KEY": "<your inbin_api_key>"
}
}
}
}
Environment variables
INBIN_API_KEYrequired secret Your Inbin API key (starts with ink_live_). Get one at https://inbin.dev/dashboard.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
@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.
Frequently asked questions
What is io.github.yaotsakpo/inbin?
Query Inbin's parsed email events (newsletters, invoices, alerts) as typed JSON tools.
How do I install io.github.yaotsakpo/inbin?
It runs as a remote server. In Claude Code: claude mcp add --transport http inbin 'https://api.inbin.dev/mcp' --header 'Authorization: <Bearer <your-inbin-api-key>>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.yaotsakpo/inbin need an API key?
Yes. It expects INBIN_API_KEY, Authorization, which you set in its configuration.
Is io.github.yaotsakpo/inbin open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.yaotsakpo/inbin?
It is published by yaotsakpo. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.