Integration

PostBin integration

PostBin is a free, credential-free service for capturing HTTP requests: create a throwaway bin, point any webhook producer at it, then read back the requests it received, either oldest-first as a queue or one at a time by id. Bins and their contents expire automatically, so it is a debugging aid rather than storage.

Connect PostBin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in PostBin.Built from the 5 PostBin tools below, on the connection you add once.

Common PostBin use cases

re-reading a payload that was already popped
capturing a webhook payload to learn its shape
tearing a throwaway bin down at the end of a test
checking a bin is still alive before waiting on it
waiting for a webhook to arrive and reading its payload
reading how long a bin has left
draining captured requests in order
referring back to a specific captured call
removing a bin that captured sensitive data
giving a third party a throwaway callback URL

What you can do with PostBin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bin, 3 operations

create_binCreate binPOSTCreates a PostBin bin and returns its id and expiry.
delete_binDelete binDELETEDeletes a PostBin bin and its captured requests.
get_binGet binGETChecks that a PostBin bin still exists and reads its expiry.

Request, 2 operations

get_request_by_idGet request by idGETReads a specific captured request from a PostBin bin by id.
shift_requestShift requestGETPops the oldest request captured by a PostBin bin.

Use PostBin from Claude Code, Cursor or Codex

Connect PostBin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its PostBin operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect PostBin

Create your workspace
Sign up free. Nothing to install.
Connect PostBin once
PostBin needs no credential, so its tools work immediately.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

PostBin integration FAQ

What can you do with the PostBin integration?

LiveContext exposes 5 operations on PostBin, covering bin and request. Common uses include re-reading a payload that was already popped, capturing a webhook payload to learn its shape and tearing a throwaway bin down at the end of a test.