---
title: "MCP Streamable-HTTP JSON-RPC endpoint"
method: POST
path: "/mcp"
---

# MCP Streamable-HTTP JSON-RPC endpoint

`POST /mcp`

## Request

- Base URL: `https://mcp.peelaway.io`
- URL: `https://mcp.peelaway.io/mcp`
- Auth: one of:
  - OAuth 2 (authorization code, authorization URL `https://api.peelaway.io/auth/oauth2/authorize`, token URL `https://api.peelaway.io/auth/oauth2/token`, scopes: `mcp:tools`)
  - HTTP bearer

Model Context Protocol server (JSON-RPC 2.0 over Streamable HTTP). OAuth-capable clients discover Peelaway sign-in from the canonical MCP endpoint; a pk_ bearer key remains available as a fallback. Methods: initialize, tools/list, tools/call. Tools: edit_image, get_job_status, get_job_result, share_image. See /mcp.json for the manifest.

## Request body

- object: A JSON-RPC 2.0 request object (or batch array).
  - `jsonrpc` '2.0'
  - `id` union
    - string
    - number
  - `method` 'initialize' | 'tools/list' | 'tools/call'
  - `params` object

## Response `200`

A JSON-RPC 2.0 response object (or batch array).

## Other responses

- `202`: Accepted (JSON-RPC notification, no response body).
- `401`: Authentication required

---

[API](https://skmtc.dev/peelaway/apis/peelaway-image-api.md) · [All operations](https://skmtc.dev/peelaway/apis/peelaway-image-api/llms.txt) · [OpenAPI document](https://skmtc.dev/peelaway/apis/peelaway-image-api/revisions/8ce45533c9d0?raw)