# Missing MCP token

> The missing_token error (401) means your MCP request had no Bearer Authorization header. Learn how to send your token correctly.

## Error code

```json
{
  "code": "missing_token",
  "docUrl": "https://doc.mor.payments.ai/errors/missing-token"
}
```

## HTTP status

401

## Cause

The request to the MCP endpoint (`/api/mcp`) had no `Authorization` header, or the header does not use the `Bearer` scheme.

## How to fix

- If you were in the middle of connecting with OAuth and your MCP client stopped waiting before you approved, your client timed out. The authorization was not rejected. Start the connect again; if you already finished signing up, you only sign in this time. See [Connect with OAuth](/mcp#connect-with-oauth).
- Connect with OAuth if your client supports it: it discovers the authorization server from the `WWW-Authenticate` header of this response. See [Connect with OAuth](/mcp#connect-with-oauth).
- Otherwise generate a `pai_mcp_*` token in **Developer Tools → MCP Tokens** and send it on every request as `Authorization: Bearer <token>`. See [Manual: User MCP Key](/mcp#manual-user-mcp-key).

## Related

- [Invalid MCP token](/errors/invalid-token)
