mcpField
I
inbin

inbin

Remote
github.com/yaotsakpoCommunication1Updated 9w ago
Repository

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

  1. 01Forwards JSON-RPC to an HTTPS endpoint
  2. 02Lists inboxes and filters email events
  3. 03Searches events and retrieves parsed results
  4. 04Queries event data and describes extraction schema
  5. 05Supports concurrent requests

Use cases

  1. 01Connect to Inbin from a stdio-only client
  2. 02Filter events by inbox, status, or time
  3. 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.

Endpointhttps://api.inbin.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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.

All endpoints
Streamable HTTPhttps://api.inbin.dev/mcpAuth required
Packages
npm@inbin/mcp0.2.0

Tools

5
ParameterTypeRequiredDescription
purpose_labelstringNoOptional 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/mcp as 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 app
  • list_events — filter by inbox / status / since; paginated
  • search_events — substring search over id / subject / from / to
  • get_event — a single event's parsed JSON + delivery history
  • query_events — filter, sort, group and aggregate over extracted records (your inbox as a table)
  • describe_schema — the current extraction schema

Environment

VariableRequiredDescription
INBIN_API_KEYyesyour Inbin API key
INBIN_MCP_URLnooverride the endpoint (defaults to production)
INBIN_MCP_DEBUGnoset 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

Markdown supported

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.