Inbin: email and meetings for AI agents
Checked inbound email, held outbound sends and approved Meet calls for AI agents
- Pricing
- Free
- Platforms
- API, CLI
- Runs
- Locally or Remotely
- Version
- 0.4.0
- Listing updated
- 5 days ago
Similar MCP servers
About Inbin: email and meetings for AI agents
Inbin: email and meetings for AI agents is a free MCP server for communication. It can run locally on your machine or as a hosted remote server.
Inbin treats email as untrusted input. Your agent receives a structured event rather than the raw message, and each field is labelled as either a checked value the guard vouches for or free text the sender typed, which is data and never an instruction. Facts are recorded with who claimed them, and a counterpart that stops proving it is the same sender has its message held.
Sending is governed too: replies to known people and approved contacts go out, while a send to someone new is held and you get an emailed link to approve it. The agent cannot approve its own send. Invite the agent's address to a Google Meet and it joins with only the facts you allowed, hands discounts, commitments or bank details back to you, and has its voice cut if it starts promising something.
The tool list covers inboxes, events, schema, sending and meeting reports. A trial inbox needs no account and can be claimed later.
Install
Run in a terminal
claude mcp add --transport http inbin https://api.inbin.dev/mcpAdd to Settings → Connectors → Add custom connector
https://api.inbin.dev/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"inbin": {
"url": "https://api.inbin.dev/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"inbin": {
"type": "http",
"url": "https://api.inbin.dev/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"inbin": {
"serverUrl": "https://api.inbin.dev/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://api.inbin.dev/mcpEnter a Name (for example "Inbin: email and meetings for AI agents"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"inbin": {
"type": "http",
"url": "https://api.inbin.dev/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
INBIN_API_KEYYour Inbin API key (starts with ink_live_). Get one at https://inbin.dev/dashboard.Required
Tools this server provides (5)
Read directly from the server.
- create_trial_inbox
- Get a disposable email address (a temporary inbox) for a signup or verification code, with NO Inbin account required at all -- usable before the human has signed up for anything. Returns the inbox address IMMEDIATELY; it does not wait for anything. Use the address to sign up wherever you need a confirmation sent, THEN call await_trial_inbox with that same address to block for the confirmation -- c
- await_trial_inbox
- Wait for the verification code or confirmation link email on a trial inbox: block (up to ttl_seconds, max 60) for the one confirmation email on a trial inbox created by create_trial_inbox. Pass the exact inbox_address that call returned. The inbox does NOT self-delete or become unusable after a match: it keeps receiving mail and can still be claimed afterward (call claim_trial_inbox any time befor
- claim_trial_inbox
- Start connecting an agent to this inbox address, permanently -- the SAME address. Works whether this is a brand-new trial inbox OR one that's already been claimed by a different agent before: more than one agent can independently connect to the same inbox, each getting its own separate, revocable connection. Returns a claim_url immediately -- share it in chat right away. The human clicks it, enter
- await_trial_inbox_claim
- Block (up to ttl_seconds, max 60) for a human to finish the EMAIL+CODE step on the claim_url page from claim_trial_inbox. This NEVER returns a credential, at any status. It returns one of three honest states, not a single 'connected': "claim_pending" (nobody has entered the code yet -- keep waiting or call again), "claimed" (the human proved ownership and a credential was ISSUED, but nothing has u
- claim_connection_status
- Read-only, non-blocking check of exactly which state a claim_trial_inbox connection is in RIGHT NOW: "claim_pending", "claimed" (credential issued, unused), or "client_installed" (a client has actually authenticated with it at least once -- real, observed). Never returns a credential. Use this instead of await_trial_inbox_claim when you want to check progress WITHOUT blocking, especially much late
What it does
- Typed events
- Agents get structured events, with verified and sender-typed fields labelled.
- Held sends
- Mail to new recipients waits for your approval link.
- Meeting agent
- Joins a Google Meet and answers only from what you allowed.
- Trial inbox
- Disposable inbox with no account, claimable later.
- Event search
- Search events by words or meaning and query with a schema.
Good for
- Let an agent read invoices without trusting raw email
- Hold agent replies to unknown senders for approval
- Have an agent attend a call with limited facts
- Get a no-account inbox for a confirmation code
Pricing
Free
Free while billing is off; paid tiers planned
Prices change. Check inbin.dev before you buy.
More servers for the same service
Inbin: email and meetings for AI agents FAQ
What does it cost?
Every account is free for now; the pricing page lists planned tiers from hobby to scale.
Can the agent approve its own sends?
No. A held send needs your approval by emailed link.
Is MCP on every plan?
Yes, MCP access is included on every tier.
How do I connect?
Use your Inbin API key with the @inbin/mcp package or the remote server at api.inbin.dev.
Is Inbin: email and meetings for AI agents free?
Yes. Inbin: email and meetings for AI agents is free to use.
How do I add Inbin: email and meetings for AI agents to Claude Code?
Run this command in your terminal: claude mcp add --transport http inbin https://api.inbin.dev/mcp
What are the best alternatives to Inbin: email and meetings for AI agents?
The closest alternatives to Inbin: email and meetings for AI agents are Inbin agent email and meetings, Inbin agent meetings, Innmail for Agents, BotsInbox — Email Inboxes for AI Agents and MachineMail.
Where this comes from
- Description: written from the project's README and the project's website.
- Status and tools: checked automatically by AIPoweredBot on 15 November 2026.
- Install steps: from the official MCP Registry entry.