Slima MCP vs file MCP vs built-in Coach

Three routes for AI to access your writing. Use the right tool for the right task.

Three routes

1 · Slima MCP

External AI (Claude / ChatGPT / Cursor) connects to Slima's cloud via MCP API:

• Reads all books on your Slima account
• Edit, create, delete files
• Cross-device consistent (cloud)
• No local files required

Best for: you already use external AI, books live in Slima

2 · File MCP (e.g. filesystem-mcp)

External AI connects to a local folder on your machine:

• Doesn't know Slima exists
• Reads .md files
• You must export Slima books to markdown first

Best for: fully local workflow, Slima just for text editing

3 · Built-in AI Coach

The chat in the right panel of the Slima editor:

• Inside Slima, no external tool
• Already sees your book (same capabilities as Slima MCP)
• No setup

Best for: writing inside the Slima editor

At a glance

	Slima MCP	File MCP	AI Coach
Setup	One-time OAuth	Point at a folder	None (built-in)
Cross-device	✅	❌ (local)	✅
Slima structure-aware	✅	❌	✅
External AI tools	✅	✅	❌
Sees version history	✅	❌	✅

Can I use them together?

Yes — Slima MCP + AI Coach is a common pairing:

• Edit big structure in Cursor (great IDE)
• Switch to Slima editor for writing prose, use the in-editor Coach

Related

• What Slima MCP is
• Pick your connection method
• AI Coach