Framebin Docs
MCP

MCP server

Endpoint, transport, authentication and protocol details.

Endpointhttps://api.framebin.co/mcp
TransportStreamable HTTP. Each request is a JSON-RPC 2.0 POST; responses are JSON.
SessionsStateless. No Mcp-Session-Id is required.
AuthAuthorization: Bearer fbm_your_key
ProtocolMCP 2025-03-26 and later
Methodsinitialize, tools/list, tools/call, ping

Initialize

curl -s https://api.framebin.co/mcp \
  -H "Authorization: Bearer fbm_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}'

Call a tool

curl -s https://api.framebin.co/mcp \
  -H "Authorization: Bearer fbm_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_screens","arguments":{"query":"paywall","platform":"iOS","limit":3}}}'

Results come back as MCP content blocks. Text blocks hold JSON; get_screen also returns an image block with the screenshot.

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{ \"total\": 41, \"screens\": [ { \"id\": \"scr-…\", \"title\": \"…\", \"app\": { \"name\": \"…\" }, \"image_url\": \"…\", \"web_url\": \"https://framebin.co/screens?screen=scr-…\" } ] }"
      }
    ]
  }
}

Other clients

Any client that supports remote HTTP MCP servers with custom headers works. ChatGPT and claude.ai custom connectors sign in with OAuth, which Framebin doesn't offer yet; use Claude Desktop or one of the tools in Client setup instead.