MCP Tools¶
Narnia exposes fifteen MCP tools: eight for working with your local Copilot CLI session history, and seven for managing Narnia-owned scheduled Copilot jobs. Use them from any AI assistant that supports the Model Context Protocol — including GitHub Copilot CLI, Claude Desktop, Cursor, and VS Code.
Session History Tools¶
| Tool | Purpose | Key Parameters |
|---|---|---|
list_recent_sessions |
List most recently updated sessions | limit |
search_sessions |
FTS5 full-text search | query, limit |
get_session_details |
Full metadata for one session | sessionId |
get_session_checkpoints |
All checkpoints for a session | sessionId |
get_session_turns |
Paginated conversation turns | sessionId, offset, limit |
get_session_workspace |
Git root and artifact file list | sessionId |
list_sessions_by_repository |
Filter by git repository | repo |
list_sessions_by_cwd |
Filter by working directory | cwd |
Looking for the web UI launcher?
The open_narnia_ui MCP tool has been replaced by the narnia-web-server skill, which provides more reliable lifecycle management with full visibility into build output.
Common Workflow¶
After a machine restart, start by listing recent sessions or searching by project name:
list_recent_sessions— scan what was running recentlysearch_sessions— narrow down by keyword or repo nameget_session_details— confirm the right session before resumingget_session_checkpoints— read the last checkpoint to restore context
All session tools return JSON. Results are read-only — Narnia never modifies your session data.
Scheduled Job Tools¶
Manage Narnia-owned scheduled Copilot jobs — recurring copilot -p runs that Windows Task Scheduler executes unattended on a daily/weekly/monthly cadence. See the narnia-scheduler skill for the full create/migrate/verify workflow built on top of these tools.
| Tool | Purpose | Key Parameters |
|---|---|---|
list_schedules |
All cataloged jobs joined to live task status | — |
get_schedule |
A single job's full catalog entry by id | id |
create_schedule |
Create a job and (by default) register its task | name, prompt, cadenceKind, time |
update_schedule |
Replace a job's definition and re-register | id, name, prompt |
set_schedule_enabled |
Enable/disable a job's task | id, enabled |
run_schedule_now |
Start a job's task immediately | id |
delete_schedule |
Remove a job's task, wrapper, and catalog entry | id |
These tools are backed by the same service as the web UI's Schedules page — creating or editing a job through either surface is immediately visible in the other.