---
title: Use Scripto in Claude Desktop
description: Add the Scripto MCP custom connector and sign in over OAuth to drive Scripto from chat — for hosts that don't live in a terminal.
---

For agents that don't live in a terminal — Claude Desktop, the claude.ai web app, ChatGPT desktop — Scripto connects as an **MCP custom connector**. You add the connector once, sign in to Scripto when prompted, and ask the assistant to work with your articles directly from chat. No CLI install, no API key to paste.

<Note>

Using Scripto from the **terminal**? See the [`scripto` CLI](/cli/overview) — it's the primary and most complete interface. The MCP connector is for hosts with a built-in "Custom Connectors" panel.

</Note>

<Warning>

**Availability.** The Scripto MCP server's tool set ships in a later release. This page describes the **connector + OAuth connect flow** so it's ready; the specific tools an assistant can call will be documented here once they land. Until then, the CLI is the supported path.

</Warning>

## How the connector works

Scripto pairs an MCP **resource server** (`scripto-mcp`) with `scripto-app` acting as the OAuth 2.1 **authorization server**. When you connect:

<Steps>

<Step title="Add the connector">

In the host's connector settings, choose **Add custom connector** and give it the Scripto MCP server URL (`https://mcp.scripto.codika.io/mcp`).

</Step>

<Step title="Sign in to Scripto">

The host opens a browser tab to Scripto's consent screen. If you're not signed in, you sign in to your Scripto account first.

</Step>

<Step title="Grant access">

Click **Allow**. The browser bounces back to the host and the connector is ready. Every action then runs **as your signed-in Scripto user**, scoped to your own articles.

</Step>

</Steps>

## What it will let you do

Once the tool set ships, you'll be able to ask the assistant to do — as your Scripto user — the same things the CLI does: list and read your articles, read an outline, read a section, read the Brief, and (with confirmation) create, edit, publish, and import. The tools map one-to-one onto the same per-user `/api/*` routes the CLI uses, so behaviour is identical across surfaces.

## Auth, in one line

The web app uses a session cookie; the CLI uses a static `scripto_` Bearer key; the MCP server uses a per-user OAuth access token that `scripto-mcp` verifies against `scripto-app` and forwards on every call. All three resolve to the same user and the same per-user authorization rule — there is exactly one source of truth.

## Manage your access

To cut off the assistant's access, remove the connector in the host's settings; the assistant can no longer call Scripto. Reconnecting later re-runs the sign-in handshake. Access can also be revoked from Scripto's side (consent revocation), which the server re-checks live.

<Note>

**Connector icon.** Because hosts render the favicon of the connector URL's registrable domain, the Scripto connector currently shows Codika's icon (the MCP server lives under `codika.io`). That trade-off is accepted for now; a dedicated Scripto root domain is the path to its own connector icon later.

</Note>

## Next

- **[Use Scripto with Claude](/guides/with-claude)** — the terminal/CLI loop (the path available today).
- **[API keys](/concepts/api-keys)** — how the CLI authenticates, alongside the OAuth path.