MCP An open door to your project

Connect your tools to your book.

Point Claude, Cursor, or your own setup straight at your Slima project, and work with your whole book from wherever you write.

Start free See how it works
Claude · connected to Slima MCP
✦ Connected project 14 tools
▾🔧 Tools
📄list_chapters
📄read_chapter
✍️write_chapter
👤get_characters
🕓list_versions
▾🔗 Clients
●Claude
●Cursor
+ Authorize app
SESSION›THE ASSASSIN

Working from your editor

You
Read chapter two and tell me if Elena's eyes stay consistent.
Claude · via Slima
I called read_chapter on Act I · 2. Rooftops. Elena's eyes are green there, and again in chapter nine. Consistent.
3 tools available on this project · token authorized
You
Good. Draft the next scene and save it to the project.
Connected: Claude
Reading your project now
⌘ Cursor
Linked over local stdio
🔧 14 tools
Read and write your book
🔑 Token authorized
Revoke any time
Works with the tools you already write in
ClaudeChatGPTCursorGemini CLIVS Code
An open door to your project

One open standard, any tool you like.

MCP is a shared language for tools to talk to apps. Slima speaks it, so your editor reaches the same full-book context Slima keeps, not a pasted snippet.

🔌

Connect your tools

Claude, Cursor, Gemini CLI, and anything that speaks the open standard.

📖

Read the whole project

Your tools get the same full-book context Slima keeps, not a fragment.

✍️

Write straight back

Draft, edit, and organize from your editor; it lands in your project.

Connect over the web

Add Slima to Claude or ChatGPT in a click.

Point a hosted client at your Slima project and authorize it once. Your book is there, ready to read and write, no install needed.

  • Works with Claude and ChatGPT connectors
  • Sign in once, authorize, and you are connected
Connect a client
Hosted, over the web
✓ Claude connected
✓ ChatGPT connected
✓ Full-book context shared read + write
✓ Token scoped to one project secure
Connect locally

Wire it into Cursor, Gemini CLI, or VS Code.

Run the connection on your own machine and your editor talks to your project directly. The same tools, right inside where you build.

  • Cursor, Gemini CLI, and VS Code over local stdio
  • Bring your own setup; if it speaks MCP, it fits
Local clients
Running on your machine
✓ Cursor stdio
✓ Gemini CLI stdio
✓ VS Code stdio
✓ Your own setup any MCP client
What your tools can do

Tools that read and write your book.

Slima exposes your project as a clean set of tools. Your client lists them, then reads chapters, drafts new scenes, and keeps everything in your project.

📖

Read

List and read chapters, with the full-book context Slima already holds.

✍️

Write

Draft and edit chapters straight from your editor; it lands in your project.

👤

Reference

Pull characters, notes, and timelines so your tool never loses a thread.

🕓

Versions

See snapshots and restore points, so nothing you write is ever lost.

What a connected tool can reach

Read the whole book free. Subscribe to let it edit.

Reading is not rationed by plan. On the free plan an assistant on your machine can already open every file in the book — chapters, characters, the world map, the timeline. What a subscription adds is letting it make the change itself.

📚

Every file type, free

No plan restricts reading. Point Claude, Cursor or your own client at a book and it sees the manuscript and the structured files behind it, rather than whatever you remembered to paste.

✍️

Editing structure comes with a plan

Screenplays, beat boards, relationship boards, world maps and timelines are edited field by field — creating, changing and removing all sit on the same line. That editing is part of the subscription plans; on the free plan the tool reads them and tells you what it would change.

👥

Team seats inherit it

A writer on a team seat gets the team's plan automatically. Nobody on the team needs a second subscription of their own to let their tools write.

File Read Edit · Free Edit · Subscription
Manuscript.md .txt ● ● ●
Screenplay.script ● — ●
Beat board.beats ● — ●
Relationship board.map ● — ●
World map.geomap ● — —
Story timeline.timeline ● — ●
Data files, images, PDFs ● — —

The last row is read-only on every plan, deliberately: a language model editing a JSON file by find-and-replace produces a file that no longer parses, so no write tool touches those. Credits bought as a one-off pack cover AI usage inside the Slima app; editing structured files over MCP goes with a plan.

Editing structured files needs a current Slima MCP package as well as a plan. If your client is pinned to an older version the tools simply are not there, which looks like nothing happening rather than a refusal — run it unpinned, or update it, and they appear.

Tokens and authorized apps

You hand out the keys, and you take them back.

Each connection runs on a token you create and scope to one project. See every authorized app in one place, and revoke any of them whenever you like.

  • One token per client, scoped to a single project
  • Review and revoke authorized apps any time
Authorized apps
You control every connection
✓ Claude read + write
✓ Cursor read + write
! Old laptop token revoke
✓ Tokens never leave your account private
Private by default

An open door that only you open.

Connecting a tool never opens your work to other users. Your book stays yours, and is never used to train models.

🔒

Private by default

Nothing is shared until you authorize a client and scope its token.

🔑

Yours to revoke

Pull any token and that client loses access at once.

🚫

Never trains models

Your project is never used to train anyone's models.

One project. Every tool.

Start free and connect your setup in minutes. Your work is never used to train models.

Start free See pricing