Slima

Slima MCP

MCP (Model Context Protocol) Server for Slima - AI Writing IDE for Novel Authors.

Connect your Slima books to any MCP-compatible AI tool - one server, all platforms.

Supported Platforms

Desktop Applications (Local MCP - stdio)

Web Applications (Remote MCP - HTTP)

MCP became the industry standard in December 2025 when Anthropic, OpenAI, and Block co-founded the Agentic AI Foundation under the Linux Foundation.

Features

Book Management

• Create new books
• List and view your books
• Get file/folder structure
• Track writing statistics

File Operations

• Read any file by path
• Edit specific text (search & replace)
• Write (replace) file content
• Create new files
• Delete files
• Append content to files
• Search across all files

AI Beta Reader

• Get feedback from virtual reader personas
• Analyze chapters with different reader perspectives

Quick Start

Pick the path that matches how you use AI:

• ⭐ Use claude.ai / ChatGPT in a web browser → Recommended: web connector *(one-time setup, auto-updates forever)*
• Use Claude Desktop / Cursor / Gemini CLI locally → Local install with npx
• Running in air-gapped / enterprise environments → Self-host

Recommended: claude.ai / ChatGPT Web (auto-updating)

If you chat with Claude or ChatGPT in a browser, this is the easiest and most future-proof option. Configure once and you will automatically get every Slima MCP update — no upgrade commands, no config edits.

MCP URL: https://mcp.slima.ai/mcp

claude.ai (Pro / Max / Team / Enterprise)

1. Sign in at claude.ai.
2. Open Settings → Connectors (or Integrations depending on your plan).
3. Click Add custom connector.
4. Fill in:

• Name: Slima
• URL: https://mcp.slima.ai/mcp

1. Click Connect → you will be redirected to slima.ai to approve → return to claude.ai.
2. The Slima tools icon appears in your chat input. You're done.

ChatGPT (Plus / Pro, Developer Mode)

1. Sign in at chatgpt.com.
2. Open Settings → Connectors → Advanced and toggle Developer Mode on (2025.10+).
3. Back in Connectors, click Create → Custom MCP Server.
4. Fill in:

• Name: Slima
• Server URL: https://mcp.slima.ai/mcp
• Authentication: OAuth

1. Click Create → approve the OAuth flow.

After setup, Slima features roll out automatically on your next conversation. No restarts, no reinstalls.

---

Local: Claude Desktop / Cursor / Gemini CLI

Use this if you want offline-friendly operation, faster startup, or you need to run MCP alongside other stdio servers.

Recommended config — pinned to the major version so you pick up new features automatically but never break on a 1.0 release:

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "slima": { "command": "npx", "args": ["-y", "slima-mcp@0"], "env": { "SLIMA_API_TOKEN": "slima_your_token_here" } } } }

Get your token from Account settings → Authorized Apps or run npx slima-mcp@0 auth once to save it to disk.

Cursor

{

"mcpServers": { "slima": { "command": "npx", "args": ["-y", "slima-mcp@0"], "env": { "SLIMA_API_TOKEN": "slima_your_token_here" } } } }

Gemini CLI

gemini mcp add slima --command "npx -y slima-mcp@0"

Or install it as a Gemini CLI extension (it asks for your API token once and keeps it in the system keychain):

gemini extensions install https://github.com/slima-ai/slima-mcp

Why `slima-mcp@0` instead of `slima-mcp` / `slima-mcp@latest`? Using @0 pins to the current major version — npx fetches new 0.x.y releases automatically (so you get features + bug fixes), but when we ship 1.0.0 with breaking changes you won't silently pick it up without updating your config. We'll announce the @1 switch in the release notes.

⚠️ This only holds if you do not also have a global `slima-mcp` install. npx pkg@

will happily satisfy the range from a package already on your PATH and never contact the

registry at all. Measured on 2026-09-09 with a global 0.2.0 present and 0.3.0 on npm:

| command | resolved |

|---|---|

| npx -y slima-mcp@0 | 0.2.0 — used the global install |

| npx -y slima-mcp | 0.2.0 — same |

| npx -y slima-mcp@latest | 0.3.0 — a dist-tag forces a registry lookup |

| npx -y slima-mcp@0.3.0 | 0.3.0 — the global can't satisfy an exact newer version |

So a stale global install makes the npx form silently stop upgrading, while the server keeps

telling you to upgrade. Remove it — see below.

Migrating from a global install

If you already installed globally with npm install -g slima-mcp:

# Remove the old global install — REQUIRED, not just tidiness.

Leaving it in place makes npx -y slima-mcp@0 resolve to the old global copy

forever (see the warning above), so you'd stay outdated while being told to upgrade.

npm uninstall -g slima-mcp

Then change your config command from "slima-mcp" to the npx form above, and restart the client.

Verify: npx -y slima-mcp@0 --version must print the version shown by npm view slima-mcp version.

⚠️ Check every place you may have installed it. A global install can exist per Node version manager environment and per OS — on WSL setups it is common to have one under nvm *and* one under Windows' AppData/Roaming/npm, at two different versions, with only one of them on the PATH your MCP client actually uses.

Or, if you want to stay on a global install, remember to periodically run:

npm install -g slima-mcp@latest

Otherwise your local client will drift from the MCP tools/schema the Slima backend exposes.

Self-host (advanced)

You can also clone this repo and deploy the Cloudflare Worker yourself. See wrangler.toml + npm run deploy:worker. Not required for normal use.

---

Remote MCP Security

The hosted Remote MCP Server at https://mcp.slima.ai/mcp uses:

• OAuth 2.0 + PKCE for authentication — no tokens copy-pasted.
• No secrets stored server-side — credentials never leave Slima's auth server.
• Session-based: OAuth tokens are stored in Cloudflare KV, scoped per session.
• Revocable anytime from Account settings → Authorized Apps: revoking an app takes effect on its next request.

---

Book Types: Writing Studio vs Script Studio

Slima books come in two flavors, distinguished by the book_type field. MCP behaves slightly differently for each:

For per-book details, ask your AI client to read the resource slima://books/{book_token}/schema — it returns a JSON spec of exactly which paths are writable/read-only for that specific book.

list_books tags every book with its studio icon (📝 / 📖) so you (and the AI) can tell them apart at a glance.

---

Available Tools

39 tools. R = read-only (never changes your book); W = changes something and says so in its description. Reads and writes are always separate tools.

Start here (teaching)

Book Management

File Operations

Every write is a commit in the book's version history, so it can be reviewed and reverted.

Structured Files (one field at a time)

Notes and Comments

AI Beta Reader

Teams

|