Search the Sasha docs

Every page of the Sasha docs, with the tab it is in and its kind.

Section
Kind

What Sasha is and what Sasha holds

Sasha by Context is Everything is a private AI knowledge base. Each organisation has its own instance, which no other organisation shares.

Use Sasha Article

Connect Claude to your Sasha

Connect Claude to your organisation's Sasha so you can search your knowledge and run Sasha recipes from Claude, never with more access than you have in Sasha.

Use Sasha Article

Who can do what in Sasha

Each person in Sasha is an admin, staff or member. See what each role can do, what an admin can change, and what a Claude connection can reach.

Use Sasha Article

Let an agent do a regular job for you

An agent does one regular job for your business, such as following up quiet customers or checking your costs, and holds its work for you to approve.

Use Sasha Article

Set up an agent, step by step

Prepare the sources, start the set-up from Agents that work for me, check the brief, choose what the agent may read, run the first report, then put it on a schedule.

Use Sasha Article

Sync a folder from GitHub into a project

Connect one folder of a GitHub repository to a Sasha project. Sasha keeps a read-only copy and refreshes it every day. Make a read-only token, add the card, and keep it working.

Use Sasha Article

Work out what to charge for an offer

Price a service, package, product, course or membership with Sasha, starting from your own pricing documents, with a fairness check and a way to test it.

Use Sasha Recipe

Connect third-party tools to Sasha

Add a service's MCP server in Sasha Settings, keep credentials out of chat, and use safe diagnostics to save, test and discover its capabilities.

Use Sasha Article

Fix a connector that does not work

What to check and change when a tool connected to Sasha, or Claude Desktop, does not do what you expect, in plain steps.

Use Sasha Article

What Claude can do with Sasha

When Claude is connected to Sasha, Claude can search and read your knowledge, run recipes and skills, use apps and, if your Sasha allows it, write documents.

Use Sasha Article

Where your data lives in Sasha

Each organisation has its own Sasha instance. See what Sasha keeps in your instance, who can reach it, and how a Claude connection reaches it.

Use Sasha Article

Sasha MCP reference

The reference for agents that use Sasha through MCP. How to connect, how scopes and roles set the tool list, and one page for each tool and tool family.

Developers and AI agents Reference

What's new

The changes to the Sasha MCP server and this reference, newest first, so an agent or a developer can see what is new since they last looked.

Developers and AI agents Reference

Scopes

Every scope of the Sasha MCP server, the consent text a person sees, and the tools each scope opens.

Developers and AI agents Reference

Find a fact and cite its source

Find a fact in the knowledge base, read the document that holds it, and give the person the fact with the path of its source document.

Developers and AI agents Reference

Run a skill and poll for the result

Start one of the organisation's skills, poll checkExecution until the run ends, and read the document that the skill saved.

Developers and AI agents Reference

Suggest an improvement and track it

Report a bug, a friction, a docs gap or a feature you need to the Sasha team, then check in a later session what happened to it.

Developers and AI agents Reference

Read and change the data of a Sasha App

Read rows from a Sasha App, total them, add a record through the app's own action, and correct one row, with a person's approval for each change.

Developers and AI agents Reference

Work with brains and blueprints

Find the brains a connection can see, learn what each kind should hold, find the gaps, and answer from a brain and its parent brains.

Developers and AI agents Reference

Write a document in your member home

Create a note in a member's own home with writeDoc, then change one passage of it with editDoc, with a version check on each change.

Developers and AI agents Reference

All tools

Every tool of the Sasha MCP server in one table: what it does, the scopes it needs, and whether it only reads.

Developers and AI agents Reference

Tools by job

Every tool and tool family of the Sasha MCP server, grouped by the job it does, with one line on what each one is for.

Developers and AI agents Reference

listProjects

List the projects this connection can see. Call it first, then pass a project id to listDocs, searchKnowledge or readDoc.

Developers and AI agents Reference

listDocs

List the documents in one project, with titles from frontmatter. Paths have no project prefix, so pass the same project to readDoc.

Developers and AI agents Reference

searchKnowledge

Find documents that contain a text, across every visible project or one. Returns paths with the project prefix, line numbers and snippets.

Developers and AI agents Reference

readDoc

Read one document, in pages of up to 50,000 bytes. Give project and path, or one path that starts with the project id.

Developers and AI agents Reference

listBrains

List the brains this connection can see, with each brain's blueprint, level, readable parent and depth by ring. Then open one with getBrain.

Developers and AI agents Reference

getBrain

Show one brain's contents page - its card, depth by ring, each document with its state and a readDoc path, and the documents it drops.

Developers and AI agents Reference

getBlueprint

List the blueprints, or show one - the plan for a kind of brain, with every document's file, title, ring, spine domains, out-of-date rule and asks.

Developers and AI agents Reference

searchBrain

Search the documents of one brain, and with includeParents its readable parent brains. Returns the brain, document title, path, line and snippet.

Developers and AI agents Reference

getDocs

Read the usage guide on this instance. Call it with no arguments for the table of contents, then once for each section you need.

Developers and AI agents Reference

suggestImprovement

Tell the Sasha team about a bug, a friction, a docs gap or a feature you need. One call for each issue. Returns an id and a FEEDBACK reference.

Developers and AI agents Reference

checkSuggestion

Read the status of an improvement suggestion by the id or the FEEDBACK reference that suggestImprovement returned. A member sees only its own connection's suggestions.

Developers and AI agents Reference

listSuggestions

List the improvement suggestions filed on this instance, newest first, with each FEEDBACK reference and what happened to it. Filter and page.

Developers and AI agents Reference

checkExecution

Poll a skill run that a skill_ tool started. Returns its status, a summary when it ends, and the path of the document it saved.

Developers and AI agents Reference

getMeetingTranscript

Read the transcript segments of a live or recent meeting by its id. For a finished meeting, read the saved document in the knowledge base.

Developers and AI agents Reference

listAppFiles

List every source file in a Sasha App package you manage, with its size and version, and the package status. Start every app change here.

Developers and AI agents Reference

readAppFile

Read the full text of one file in a Sasha App package you manage, with its version. Pass that version to the tool that changes the file.

Developers and AI agents Reference

writeAppFile

Create a new file in a Sasha App package, or replace a whole file. The change is live at once, with no draft and no undo, and the result says if the app still validates.

Developers and AI agents Reference

editAppFile

Replace one exact passage in a Sasha App source file. The passage must occur exactly once. Live at once, with no undo; the result says if the app still validates.

Developers and AI agents Reference

deleteAppFile

Delete one file from a Sasha App package you manage. Never APP.md. Remove every reference to the file first. Live at once, with no undo.

Developers and AI agents Reference

checkApp

Validate a whole Sasha App package you manage again. Says whether the app is live, or lists each problem by file, line, code and reason.

Developers and AI agents Reference

listSchedules

List every schedule on this Sasha: its skill, when it runs and in which time zone, whether it is on, its last and next run, and the last error.

Developers and AI agents Reference

createSchedule

Add a schedule that runs a skill at set times in a time zone. One skill can have several schedules, one for each time it must run.

Developers and AI agents Reference

updateSchedule

Change a schedule: pause or restart it, or change its skill, time, time zone or time limit. Send only the fields that change.

Developers and AI agents Reference

deleteSchedule

Delete a schedule. The skill itself is not changed. To stop a schedule for a time and keep it, pause it with updateSchedule instead.

Developers and AI agents Reference

runSchedule

Start one run of a schedule now, to test it. It returns at once; call listSchedules after a few minutes for the result.

Developers and AI agents Reference

syncFolder

Sync a folder that Sasha copies from GitHub now, and see the commit, the time of the last good sync and any error. Admin only.

Developers and AI agents Reference

createClaudeDesktopJob

Prepare a job for Claude Desktop to do in the person's own browser. The person approves the whole text in a Confirm box before it is saved.

Developers and AI agents Reference

checkClaudeDesktopJob

Read a Claude Desktop job's status, the questions Claude Desktop asked and its report, from the chat that prepared the job.

Developers and AI agents Reference

recordClaudeDesktopJobCheck

Record Sasha's own check of a reported Claude Desktop job, checked or failed with a short summary, from the chat that prepared the job.

Developers and AI agents Reference

listMyClaudeDesktopJobs

List the Claude Desktop jobs the person approved in Sasha that are not finished yet: ready, claimed or needs_you, newest first, at most 20.

Developers and AI agents Reference

getClaudeDesktopJob

Read the whole text of one approved Claude Desktop job, exactly as the person approved it, and start it: a ready job becomes claimed.

Developers and AI agents Reference

askAboutClaudeDesktopJob

Record a question about a job you are doing, so Sasha keeps it with the job and the job shows needs_you. Ask the person in Claude Desktop too.

Developers and AI agents Reference

reportClaudeDesktopJob

Send your report on a Claude Desktop job back to Sasha when you finish or cannot go on. The job becomes reported, and Sasha starts its own check.

Developers and AI agents Reference

getTeamActivity

Per-person activity on this Sasha for the last hours: sign-in, chats, messages, skill runs, tool calls, document writes, app and agent runs, tokens and cost.

Developers and AI agents Reference

Skill tools (skill_<name>)

One tool for each skill the organisation enables for external use. A call starts the skill in the background and returns an executionId to poll.

Developers and AI agents Reference

Document write tools (writeDoc, editDoc)

writeDoc and editDoc create and change documents in a member's home or a shared project the person may write to. Off by default on every instance.

Developers and AI agents Reference

App opener tools (open_app__<app>)

One tool for each Sasha App this person can use. A call opens the app's view in a client that shows MCP Apps, and returns the app id and its live revision.

Developers and AI agents Reference

App action tools (app__<app>__<action>)

One tool for each action that a Sasha App exposes to the model, such as logging hours. An action that changes data needs a person to confirm it first.

Developers and AI agents Reference

App table tools (app__<app>__<table>__<op>)

Six tools for each table of a Sasha App that stores data, to list, get, aggregate, create, update and delete rows. A change needs a person to confirm it.

Developers and AI agents Reference

Workspace tool (createProject)

createProject creates a Sasha workspace for a knowledge project, or confirms it exists, so its documents show in the sidebar. Admin and staff only.

Developers and AI agents Reference

What Sasha is and how to work with it

The "overview" section of the Sasha MCP usage guide, as getDocs returns it: What Sasha is and how to work with it.

Developers and AI agents Reference

The knowledge base

The "knowledge" section of the Sasha MCP usage guide, as getDocs returns it: The knowledge base.

Developers and AI agents Reference

Creating and editing documents

The "writing" section of the Sasha MCP usage guide, as getDocs returns it: Creating and editing documents.

Developers and AI agents Reference

Editing the source of a Sasha App

The "apps-authoring" section of the Sasha MCP usage guide, as getDocs returns it: Editing the source of a Sasha App.

Developers and AI agents Reference

What this connection is allowed to do

The "permissions" section of the Sasha MCP usage guide, as getDocs returns it: What this connection is allowed to do.

Developers and AI agents Reference

Running skills

The "skills" section of the Sasha MCP usage guide, as getDocs returns it: Running skills.

Developers and AI agents Reference

Limits and behaviour

The "limits" section of the Sasha MCP usage guide, as getDocs returns it: Limits and behaviour.

Developers and AI agents Reference

Brains and blueprints

The "brains" section of the Sasha MCP usage guide, as getDocs returns it: Brains and blueprints.

Developers and AI agents Reference

Research runs for a business brain

The "surveys" section of the Sasha MCP usage guide, as getDocs returns it: Research runs for a business brain.

Developers and AI agents Reference

Schedules: run a skill at set times

The "schedules" section of the Sasha MCP usage guide, as getDocs returns it: Schedules: run a skill at set times.

Developers and AI agents Reference

What Sasha can do

The "what-sasha-can-do" section of the Sasha MCP usage guide, as getDocs returns it: What Sasha can do.

Developers and AI agents Reference

Prompts

The recipe prompts that the Sasha MCP server offers. Each one is a worked example of a common job.

Developers and AI agents Reference

Resources

The resource templates of the Sasha MCP server: help articles and the data of Sasha Apps, with the scope each one needs.

Developers and AI agents Reference

Stripe

Developers and AI agents Page

Built with BernardCookie settings