TMPKIT FOR DEVELOPERS

An inbox for your next workflow.

Receive test emails, inspect mail configuration and connect your agent through one API. Your tools share one account and one allowance.

Start with the API

Create a key in the console. Store it in TMPKIT_API_KEY, then create a mailbox. Reuse an idempotency key when retrying the same creation.

# Create one mailbox; repeat with the same key on retry.
curl 'https://tmpkit.com/api/v1/mailboxes' \
  -H "Authorization: Bearer $TMPKIT_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: my-first-inbox' \
  -d '{"label":"Signup test"}'

Send from your own test system, then list messages or wait up to 20 seconds. A timeout is a normal result, not a failed delivery claim.

Connect with MCP

Use this URL in a client supporting Streamable HTTP and OAuth. Review permissions before connecting.

https://tmpkit.com/mcp

Codex CLI

codex mcp add tmpkit --url https://tmpkit.com/mcp
codex mcp login tmpkit
codex mcp list

Use a different name if tmpkit is already configured for another server. Open a new client session, then call get_capabilities and get_usage to check the connection without consuming tool allowance.

Local stdio option: download the bundle and follow tmpkit-mcp/README.md. Run npm install --omit=dev in that directory, then configure your client to run node /absolute/path/tmpkit-mcp/index.mjs with TMPKIT_API_KEY in its environment. Requires Node.js 20+. The package is distributed as a download.

Skill installation

Copy the extracted tmpkit folder to your client's skills directory; for Codex, use ~/.agents/skills/tmpkit/. It guides email verification, diagnostics and local utilities. The helper needs Python 3.10+. Credentials stay in the environment.

Predictable usage

Fixed allowances, bounded waits and no automatic overage charges.

Private resources

Mailboxes belong to your project. Keys and OAuth grants can be revoked.

Temporary by design

Receive-only mailboxes expire. Use a stable address for account recovery.