Sasha MCP reference

Scopes

A connection lists only the tools its scopes open. The consent text is what a person sees when they approve the connection. A scope marked "by name only" is never in a default grant: a client must ask for it by name.

ScopeConsent textToolsBy name only
knowledge:readRead the knowledge base (projects, documents, search)listProjects, listDocs, searchKnowledge, readDoc, listBrains, getBrain, getBlueprint, searchBrain, writeDoc, editDoc, surveyPublicContext, checkSurvey, createProjectno
knowledge:writeCreate and edit documents in the knowledge base where you have write accesswriteDoc, editDoc, surveyPublicContext, checkSurvey, createProjectno
skills:runRun skills that are enabled for external usecheckExecution, skill_<name>no
meetings:readRead meeting transcripts and documentsgetMeetingTranscriptno
improvements:adminExport improvement suggestions and write their dispositions (admin only)no MCP toolyes
apps:invokeRead and change records in Sasha Apps you can uselistAppFiles, readAppFile, writeAppFile, editAppFile, deleteAppFile, checkApp, open_app__<app>, app__<app>__<action>, app__<app>__<table>__{list,get,create,update,delete,aggregate}, app__<app>__{run_now,read_work_log,save_brief,edit_draft,bin_draft,bin_drafts,send_draft,list_schedule,schedule_drafts,stop_schedule,set_draft_day}no
apps:writeEdit the source files of Sasha Apps you manage (admin and staff only)listAppFiles, readAppFile, writeAppFile, editAppFile, deleteAppFile, checkAppno
skills:run-containedRun the research and drafting skills that are enabled for members, writing only into documents you own and never replacing onesurveyPublicContext, checkSurveyyes
schedules:manageList, add, change, delete and run the schedules that run skills for the whole organisation (admin and staff only)listSchedules, createSchedule, updateSchedule, deleteSchedule, runScheduleno
synced-folders:syncSync a folder that Sasha copies from GitHub now, and see its last commit and any error (admin only)syncFolderyes
jobs:createPrepare Claude Desktop jobs from a Sasha chat. Each job waits for your approval in Sasha.createClaudeDesktopJob, checkClaudeDesktopJob, recordClaudeDesktopJobCheckyes
jobs:runSee the Claude Desktop jobs you approved in Sasha, and send their questions and reports back to Sasha.listMyClaudeDesktopJobs, getClaudeDesktopJob, askAboutClaudeDesktopJob, reportClaudeDesktopJobno
usage:read-teamSee who used this Sasha and how much: per-person sign-ins, chats, skill runs, tool calls, tokens and cost (admin, or staff an admin allowed)getTeamActivityyes

getDocs, suggestImprovement, checkSuggestion and listSuggestions need no scope.

Built with BernardCookie settings