---
title: "MCP Endpoint"
method: POST
path: "/v1/mcp"
tags: ["MCP"]
---

# MCP Endpoint

`POST /v1/mcp`

## Request

- Base URL: `https://api.postlake.dev`
- URL: `https://api.postlake.dev/v1/mcp`
- Auth: `bearerAuth` (a scheme the document does not define)

Model Context Protocol JSON-RPC endpoint. PREFER `POST /mcp`: it is the canonical URL and now accepts either an API key or an OAuth access token, so there is no longer a reason to choose between two paths. This one is kept working for configs already pointing at it. The same tool registry covers publishing, scheduling, validation, media, notifications, comments, direct messages, engagement, profile and channel management, and analytics. See https://docs.postlake.dev/mcp for the full toolset and authentication options.

## Request body

- object
  - `jsonrpc` '2.0', required
  - `method` string, required
  - `params` object
  - `id` union
    - string
    - number

## Response `200`

Success

- object
  - `jsonrpc` '2.0', required
  - `result` object
  - `error` object
    - `code` integer, required
    - `message` string, required
    - `data` object
  - `id` union
    - string
    - number

## Other responses

- `204`: Notification success
- `401`: Unauthorized

---

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