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

1. Install

npm install -g slima-mcp

Or run directly with npx:

npx slima-mcp

2. Get Your API Token

slima-mcp auth

This will open your browser to authenticate with Slima. Your token will be saved automatically.

Or manually:

1. Go to Slima Settings
2. Click "Generate API Token"
3. Copy the token

3. Configure Your AI Tool

If you used slima-mcp auth, the token is saved automatically. Just add:

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"]
    }
  }
}

That's it! No environment variables needed.

Cursor

Add to Cursor's MCP configuration:

{
  "mcpServers": {
    "slima": {
      "command": "npx",
      "args": ["-y", "slima-mcp"]
    }
  }
}

Gemini CLI

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

If you prefer to use environment variables instead of slima-mcp auth:

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

Get your token from Slima Settings.

4. Restart Your AI Tool

After saving the configuration, restart the application to load Slima MCP.

Web Applications (Remote MCP)

For web-based AI tools like Claude.ai and ChatGPT, use our hosted Remote MCP Server.

One-Click Connection

1. In your AI tool, add a new MCP server
2. Enter the URL: https://mcp.slima.ai/mcp
3. Click "Connect" - you'll be redirected to Slima
4. Log in (or sign up) and click "Allow"
5. Done! No token copying needed

How It Works

┌─────────────────────────────────────────────────────────┐
│  Claude.ai / ChatGPT Web                               │
│                                                         │
│  1. Click "Connect MCP Server"                          │
│  2. Enter: https://mcp.slima.ai/mcp           │
│     ↓                                                   │
│  3. Redirect to Slima login                            │
│     ↓                                                   │
│  4. Approve authorization                              │
│     ↓                                                   │
│  5. Automatically connected!                           │
│                                                         │
│  No API tokens. No configuration. Just works.          │
└─────────────────────────────────────────────────────────┘

Security

• OAuth 2.0 + PKCE: Industry-standard secure authentication
• No Secrets Stored: The server never stores your credentials
• Session-Based: Your token is stored securely in Cloudflare KV
• Revocable: Revoke access anytime from Slima Settings

Available Tools

Book Management

File Operations

AI Beta Reader

Usage Examples

Once configured, you can ask your AI:

Book & Content:

• "Create a new book called 'My Novel'"
• "List my books in Slima"
• "Show me the structure of my novel"
• "Read chapter 3 of my book"
• "What are my writing stats?"

File Operations:

• "Read the character profile for my protagonist"
• "Edit chapter 1 and change 'John' to 'James'"
• "Create a new file called worldbuilding.md with notes about the magic system"
• "Search for all mentions of 'blue eyes' in my book"
• "Append this new paragraph to chapter 5"

AI Feedback:

• "Get feedback on chapter 5 from a young reader perspective"
• "Analyze my opening scene from a critic's perspective"

CLI Commands

slima-mcp auth      # Authenticate with browser (recommended)
slima-mcp status    # Check authentication status
slima-mcp logout    # Remove saved credentials
slima-mcp --help    # Show help
slima-mcp --version # Show version

Token is stored in ~/.slima/credentials.json with secure permissions.

Environment Variables

*Not required if you used slima-mcp auth

Development

Local CLI Development

# Clone the repository
git clone https://github.com/slima-ai/slima-mcp.git
cd slima-mcp

# Install dependencies
npm install

# Build CLI
npm run build

# Run tests
npm test

# Run in development mode
npm run dev

Cloudflare Worker Development

# Build the Worker
npm run build:worker

# Run Worker locally
npm run dev:worker

# Deploy to Cloudflare
npm run deploy:worker

# Deploy to preview environment
npm run deploy:worker:preview

Project Structure

slima-mcp/
├── src/
│   ├── core/           # Shared core modules
│   │   ├── api/        # Slima API Client
│   │   ├── tools/      # MCP Tool implementations
│   │   └── utils/      # Utilities and errors
│   ├── cli/            # CLI entry point (stdio transport)
│   │   ├── index.ts    # CLI main
│   │   ├── auth.ts     # Authentication commands
│   │   └── server.ts   # MCP Server for CLI
│   └── worker/         # Cloudflare Worker (HTTP transport)
│       ├── index.ts    # Worker entry point
│       └── oauth.ts    # OAuth 2.0 + PKCE client
├── wrangler.toml       # Cloudflare Worker config
├── tsup.config.ts      # CLI build config
└── tsup.worker.config.ts # Worker build config

Security

• API tokens are stored locally and never shared
• All communication with Slima API uses HTTPS
• Tokens can be revoked anytime from Slima settings

Release & Deployment

npm (Automatic)

Merge to main with a version bump in package.json triggers automatic npm publish via GitHub Actions.

# 1. Bump version on dev branch
npm version patch   # 0.1.10 → 0.1.11

# 2. Merge to main
git checkout main && git merge dev && git push

# 3. CI runs tests → publish.yml publishes to npm + creates git tag

Cloudflare Worker (Manual)

Worker deployment is separate from npm. Deploy after code changes:

npm run deploy:worker           # Production (mcp.slima.ai)
npm run deploy:worker:preview   # Staging

MCP Registry (Manual)

To publish/update the server listing on the MCP Registry:

mcp-publisher login github
mcp-publisher publish

Requires mcpName in package.json and server.json in repo root.

Operational Notes

Debugging Worker OAuth

When troubleshooting claude.ai or ChatGPT connector issues:

# Live logs from production Worker
wrangler tail slima-mcp

All OAuth endpoints log key parameters (client_id, redirect_uri, token prefix, etc.) to help trace the flow.

Worker OAuth Flow (claude.ai / ChatGPT)

Client POST /mcp → 401 + WWW-Authenticate header
  → Client GET /.well-known/oauth-protected-resource
  → Client GET /.well-known/oauth-authorization-server
  → Client POST /register (DCR)
  → Client redirects user to GET /authorize
    → Worker redirects to Rails OAuth
    → User authorizes → Rails redirects to Worker /callback
    → Worker issues auth code → redirects to client callback
  → Client POST /token (exchange code for access_token)
  → Client POST /mcp (Authorization: Bearer {access_token})

Known Constraints

• Worker Bearer token validation accepts all non-empty tokens (not just slima_ prefix) to support OAuth-issued tokens. Rails API performs actual validation.
• getTokenFromSession() checks Authorization header first, then falls back to cookie session.
• MCP Inspector (npx @modelcontextprotocol/inspector) is useful for testing the full OAuth flow independently.

License

MIT

Links

• Slima Website
• Slima App
• MCP Documentation
• MCP Registry
• Report Issues