> For the complete documentation index, see [llms.txt](https://docs.ui-color-palette.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ui-color-palette.com/mcp/authentication.md).

# Authentication

Palette generation tools work without any credentials. Community tools — publishing, updating, deleting, or listing your own palettes — require a valid UI Color Palette account.

## How it works

The server implements **OAuth 2.0** with dynamic client registration. The authorization server is Supabase, proxied through the MCP worker so that MCP clients see a single issuer.

| Endpoint            | Path                                      |
| ------------------- | ----------------------------------------- |
| Discovery           | `/.well-known/oauth-authorization-server` |
| Client registration | `/oauth/register`                         |
| Token exchange      | `/oauth/token`                            |
| MCP                 | `/mcp`                                    |

MCP clients that support OAuth 2.0 (Claude Desktop, Cursor, etc.) handle the full flow automatically — you just sign in when prompted.

## Bearer token

If your client does not handle OAuth automatically, you can pass an access token directly:

```http
Authorization: Bearer <your-access-token>
```

The token is read from the `Authorization` header on the `/mcp` request and stored in durable state for the duration of the session.

## Which tools require authentication

| Tool                          | Auth required |
| ----------------------------- | ------------- |
| `get_palette`                 | No            |
| `get_color_system`            | No            |
| `create_color_harmony`        | No            |
| `extract_dominant_colors`     | No            |
| `generate_code`               | No            |
| `generate_colors_from_prompt` | No            |
| `preview_palette`             | No            |
| `list_published_palettes`     | No            |
| `list_my_published_palettes`  | **Yes**       |
| `get_published_palette`       | No            |
| `publish_palette`             | **Yes**       |
| `update_published_palette`    | **Yes**       |
| `share_published_palette`     | **Yes**       |
| `unshare_published_palette`   | **Yes**       |
| `unpublish_palette`           | **Yes**       |

When a tool requires authentication and no token is present, the server returns:

```json
{ "error": "Authentication required. Please sign in via OAuth to use this tool." }
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ui-color-palette.com/mcp/authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.