Slima MCP

MCP behavior by studio: full matrix

4 min read

The two Slima Studios behave differently under MCP. Here's the matrix.

Slima home page showing three studios — this article compares MCP behavior between Writing and Script Studios

Full matrix

Operation Writing Studio book Script Studio book
create_book ✅ type: novel etc ✅ type: script
list_books ✅ ✅
get_book / get_book_structure / get_writing_stats ✅ ✅
read_file ✅ any path ✅ any path
search_content ✅ ⚠️ excludes .scene etc by default (needs include_structured: true)
edit_file / write_file / create_file / append_to_file ✅ any path ⚠️ only .script_studio/planning/**/*
delete_file ✅ ⚠️ only .script_studio/planning/**/*
analyze_chapter ✅ ⚠️ doesn't support structured scenes

Why Script Studio is stricter

Writing Studio = plain markdown — AI editing markdown is safe.

Script Studio = structured data (scene JSON, character JSON, storyline tree…) — wrong edits break the schema and the Slima app won't open the book.

So structured files (*.scene / *.character / series.json etc.) are read-only over MCP — must be edited in the Slima Script Studio UI.

Except .script_studio/planning/ — the AI-writable scratch space for outlines, mind-maps, research notes.

How to know a book's schema

Call slima://books/{book_token}/schema resource → exact read-only / writable path rules.

See: Schema resource

Writing to a read-only path

edit_file on a read-only path (e.g. *.scene) → 400 INVALID_PATH, no partial write.

See: Script Studio structured protections

Related

Was this helpful?