# Authoring with your AI

> Advanced: bulk-authoring decks through the MCP server.

> **Advanced, and optional.** This page is for creators comfortable with a command line
> and an AI coding assistant (Claude, and similar). You never need it — the
> [editor](https://www.deckberry.com/creators/guide/workflow/editor-tour/) makes every deck by hand. It's here
> for when you're building at volume.

## What & why

Deckberry offers a **bring-your-own-AI** authoring path: an **MCP server** your AI
assistant connects to, so you can turn notes, a CSV, or a rough list into cards by
describing what you want. Your own assistant does the writing; Deckberry just exposes
the tools it drives. There's no generation UI and no AI cost on our side — it's your
assistant, working against your account.

It's built for **scale**: seeding a large deck, reshaping many cards at once, importing
from existing material. For a handful of cards, the editor is faster.

## The one safeguard to know

**Publishing is never automated.** The tools can create decks and add or revise cards,
but nothing can flip a deck public — that stays a deliberate human click in the
editor. So you can let an assistant draft freely, then review and publish yourself,
without any risk of half-finished work going live.

## Setting it up

1. Your account must be a **creator** account.
2. In the editor, open the **API tokens** page and generate a personal access token.
   It's shown once — copy it somewhere safe.
3. Add the server to your AI client. In Claude Code, for example:

   ```
   claude mcp add --transport http deckberry \
     https://studio.deckberry.com/mcp \
     --header "Authorization: Bearer <your-token>"
   ```

Your assistant can now see your decks and author into them. Revoke the token any time
from the same page.

## Etiquette

The AI is a fast typist, not a deck designer — **every rule in this guide still
applies.** One fact per card, fronts that ask, answers you can grade: the assistant
won't enforce them, so you do, on review. Treat its output as a first draft, read every
card, and run the [publish checklist](https://www.deckberry.com/creators/guide/workflow/publish-checklist/)
before you go live. Be reasonable with volume, too — the server is rate-limited, and a
good deck is edited, not just generated.

## Related

- [Editor tour](https://www.deckberry.com/creators/guide/workflow/editor-tour/)
- [Publish checklist](https://www.deckberry.com/creators/guide/workflow/publish-checklist/)
- [The 10-minute overview](https://www.deckberry.com/creators/guide/getting-started/overview/)

---

[Read this guide on Deckberry](https://www.deckberry.com/creators/guide/workflow/authoring-with-ai/)