Changelog

Slima MCP Server is live — read and write your books from Claude, Cursor, and Claude Code

4 min read T Tim
Available in: English 한국어 繁體中文 Español العربية

We’re excited to announce — Slima MCP Server is live.

Starting this week, you don’t need to open Slima to interact with your books. Claude.ai, Cursor, Claude Code, Gemini CLI, and any other MCP-compatible AI client can read and write directly to your Slima books.

This post is longer than usual — because this change is bigger than a typical feature.

What MCP is

Model Context Protocol is an open standard that lets AI clients (like Claude.ai or Cursor) talk to external tools and data.

Think of it as USB-C for AI — one standard port, every compatible tool plugs in.

Slima MCP Server exposes your books — chapters, characters, scenes, world settings, version history — as an MCP toolset. Any MCP client can read and write through the standard protocol.

What you can do with Slima MCP

Once connected, you can do all of this from your AI client of choice:

  • Read chapters: “Show me the second half of chapter 3 in Above the Clouds”
  • Edit chapters: “Add a paragraph at the end of chapter 5 where the protagonist says goodbye to Aiden”
  • Read structure: “List all chapters in this book with word counts”
  • Create new books, chapters, or characters
  • Time-travel: “What did chapter 7 look like two weeks ago?”
  • Cross-book search: “Which of my books mentions the place name ‘Qingyang Tower’?”

In other words — your books live in Slima, but you can use them from any AI tool.

How to connect

Option 1: Claude.ai (easiest)

We spent a week building the full OAuth 2.0 flow (Dynamic Client Registration, OpenID Connect discovery) so Claude.ai connects in one click:

  1. Claude.ai → Settings → Connectors → Add custom connector
  2. Paste: https://slima.ai/mcp
  3. Click OAuth authorize, sign in to Slima
  4. Done — talk to your books inside Claude

Option 2: Claude Code (CLI)

claude mcp add slima https://slima.ai/mcp

Run through OAuth once and you’re set.

Option 3: Cursor / Gemini CLI / any MCP client

Any client that speaks MCP can connect. Manual setup at slima.ai/mcp.

Why this matters for long-form writers

The bottleneck for long-form writing isn’t “no tools.” It’s “too many tools — your thinking gets fragmented across them.”

  • Drafting in Slima
  • Looking up references in Claude
  • Debugging worldbuilding in Cursor
  • Searching the web in your browser

Every context switch is a cognitive restart.

Slima MCP fixes this — your book moves from “data inside Slima” to “extended memory of your favorite AI client.” You write in Slima; when you discuss plot with Claude, Claude can already see your manuscript. No copy-paste, no re-explaining context.

This is where we think long-form writing tools are heading. We chose to get there a little earlier.

Security

  • OAuth 2.0 with scoped permissions (read-only or read-write)
  • Revoke any connector anytime in Slima Settings → Connectors
  • All MCP operations are logged in your audit trail (“Claude.ai modified chapter 3 at 2026-01-30 14:32”)

Next month

February’s theme: Slima leaves the browser. The desktop app ships — auto-update, native menus, Gatekeeper handling.

Related Articles