---
title: "Create Mcp Token"
method: POST
path: "/api/v1/auth/app/{app_id}/mcp-token"
tags: ["Authentication"]
---

# Create Mcp Token

`POST /api/v1/auth/app/{app_id}/mcp-token`

Create an MCP Token

## Path parameters

- `app_id` string, required — The Application's ID or UID.

## Headers

- `idempotency-key` string

## Request body

- CreateMcpTokenIn
  - `expiry` integer, nullable — How long the token will be valid for in seconds.

## Response `200`

- CreateMcpTokenOut
  - `token` string, required — The MCP access token. Pass it to the MCP server as `Authorization: Bearer <token>`. It also encodes the application id, so the server needs nothing else to identify the app.
  - `slug` string, required — URL-safe slug derived from the customer's app portal display name (or the organization name when it isn't set). The client builds the MCP server name (`<slug>-webhooks`) from it. The server URL itself is `/app/<app_id>`, which is what keeps servers distinct.

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `422` — Validation Error
- `429` — Too Many Requests

---

[API](https://skmtc.net/svix/apis/svix-api.md) · [All operations](https://skmtc.net/svix/apis/svix-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/svix/svix-api/revisions/16dbcc056c48/schema)