Log inSubmit server
Slima logo

Slima

Connects MCP-compatible AI clients to Slima books for writing, file management, search, planning, and editorial collaboration.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Slima

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "slima": {
      "command": "npx",
      "args": [
        "-y",
        "slima-mcp@0"
      ],
      "env": {
        "SLIMA_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 39 tools correctly (11d ago).

Overview

slima MCP server connects MCP-compatible AI clients to Slima books through local stdio or the hosted HTTP endpoint. It lets agents create and inspect books, read and modify manuscript files, search content, manage writing plans, and work with notes and editorial comments. Use it when an AI assistant needs structured access to a Slima writing project rather than isolated chat-based feedback. Writing Studio books support broader MCP editing, while Script Studio permissions are restricted by file type and path.

Use cases

  • Create and organize a Slima writing project
  • Edit manuscript files with targeted replacements
  • Search a book for exact or related passages
  • Update timelines, beat boards, and world maps
  • Review notes and resolve editorial comments

Key features

  • Book creation and structure inspection
  • Read, write, append, edit, and delete file operations
  • Exact-text and semantic content search
  • Writing guides and craft skill loading
  • Planning artifact and relationship map updates
  • Notes and editorial comment management

Tools39

What Slima lets your agent do. Expand a tool for its parameters.

Verified live~9.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 64d

What it can do

From the 39 tools this server returned when we ran it; 39 declare their own safety hints.

Can delete or modify data · 10Writes files · 8Handles credentials · 2Makes network requests · 5Read-only tools · 28
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age275 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · slima-mcp@0 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit17d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed39Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Slima works

What slima MCP server does

slima connects AI clients to books stored in Slima, an AI writing IDE for novel authors. It exposes book management, manuscript file operations, writing guidance, search, planning artifacts, relationship maps, notes, and editorial comments through MCP tools.

The server works with both Writing Studio and Script Studio books, but the two formats have different permissions. Writing Studio books can be created through MCP and support reading and writing across paths. Script Studio books must be created in the Slima application, and MCP writes are limited to the .script_studio/planning/**/* area.

How it works

Local clients launch the package as a stdio MCP server, commonly through npx. The hosted endpoint is available at https://mcp.slima.ai/mcp for clients that support remote MCP over HTTP. Remote connections use OAuth 2.0 with PKCE; local connections can authenticate with a Slima API token or a token saved by the package's authentication command.

After connection, an AI client can discover the server's capabilities, inspect available guides and writing skills, select a book, and operate on its files. Reading and writing are represented by separate tools. The server also exposes a per-book schema resource at slima://books/{book_token}/schema, which describes the paths permitted for that book.

Setup and configuration

For Claude Desktop or Cursor, configure an MCP server that runs npx -y slima-mcp@0 and provide SLIMA_API_TOKEN in its environment. The token can be obtained from Slima account settings, or authentication can be initiated with npx slima-mcp@0 auth. Gemini CLI can add the server with its MCP command or install the repository as an extension.

Web use is configured by adding https://mcp.slima.ai/mcp as a custom connector in Claude.ai or ChatGPT Web and completing the OAuth approval flow. The hosted connection does not require a token to be copied into the client. A self-hosted deployment is also possible by deploying the repository's Cloudflare Worker with Wrangler.

Use a major-version package range deliberately. A global slima-mcp installation can cause npx to reuse an older local copy, so global installations should be removed or updated when using the npx configuration.

Tools and capabilities

  • Inspect server capabilities, guides, and writing skills, then load selected guidance in full.
  • Create books, list them with pagination, inspect metadata and structure, and retrieve writing statistics.
  • Read chapters or arbitrary files; create, replace, edit, append to, and delete files where permissions allow.
  • Search exact text across a book or find passages by semantic similarity.
  • View and update relationship maps, beat boards, timelines, scripts, and world maps.
  • List and create author notes, create editorial comments, and resolve comment threads.

Limitations and notes

Script Studio books cannot be created through MCP. Structured Script Studio files, including character, scene, storyline, note, location, season, and episode files, are read-only through MCP; changes must be made in the Slima application. MCP writes for Script Studio are restricted to planning paths.

For Script Studio search, structured files are excluded unless include_structured: true is supplied. Chapter analysis through the AI Beta Reader applies to Writing Studio books and is not supported for structured Script Studio scenes. Deleting a file or folder is limited to files and empty folders.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Slima

slima is an MCP server that connects MCP-compatible AI clients to Slima books. Its main tools manage books, read and edit files, search manuscript content, load writing guidance, update planning artifacts, and handle author notes and editorial comments. It supports local stdio connections and a hosted HTTP endpoint.

Install it through an MCP client using `npx -y slima-mcp@0` for local stdio use. Configure `SLIMA_API_TOKEN`, or run `npx slima-mcp@0 auth` to save credentials. Web clients can instead connect to `https://mcp.slima.ai/mcp` through their custom connector settings.

Yes, slima works with Cursor through a local stdio configuration. Add an MCP server that runs `npx -y slima-mcp@0` and pass `SLIMA_API_TOKEN` in the environment, then restart or reload Cursor so the tools become available.

Yes, but Script Studio editing is restricted. MCP can write only beneath `.script_studio/planning/**/*`; structured files such as scenes, characters, storylines, and episodes remain read-only and must be changed in the Slima application.

Connect it by adding `https://mcp.slima.ai/mcp` as a custom connector in Claude.ai and completing the Slima OAuth approval flow. The hosted endpoint uses OAuth 2.0 with PKCE, so you do not need to paste an API token into Claude.ai.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSlima AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/slima?style=directory)](https://allmcps.com/mcp/slima)
HTML Embed
<a href="https://allmcps.com/mcp/slima"><img src="https://allmcps.com/api/badge/slima?style=directory" alt="Slima on AllMCPs" /></a>