# Workspaces

> List the organizations and workspaces your Nodaro account belongs to and choose where an AI assistant's work lands, with list_workspaces and select_workspace.

Source: https://nodaro.ai/docs/mcp/tools/workspaces

The **workspace tools** choose where an assistant's work lands when your Nodaro account belongs to an organization, such as a school or a team. In the web app you choose a workspace in a switcher; an MCP client has no switcher, so `list_workspaces` answers "where can I work?" and `select_workspace` answers "work there". Read more about organizations in [Workspaces](https://nodaro.ai/docs/concepts/workspaces).

The tools exist only on Nodaro Cloud instances where organizations are switched on. Everywhere else they are absent, so a client learns that workspaces do not apply instead of finding a switch that does nothing. Connections authorized before organizations existed do not have the workspace permissions; remove the connector and add it again to grant them.

## `list_workspaces`

Returns the organizations and workspaces your account belongs to, and the workspace the session works in now.

**Permission:** `workspaces:read`. **Credits:** free. **Nodaro Cloud only.**

This tool has no parameters.

**Returns:**

```json
{
"workspaces": [
{ "id": "uuid", "orgId": "uuid", "name": "Class 1", "slug": "class-1", "role": "member", "memberStatus": "active", "archived": false }
],
"organizations": [
{ "id": "uuid", "slug": "kent-high", "name": "Kent High", "kind": "school", "status": "active", "role": "owner" }
],
"selectedWorkspaceId": "uuid"
}
```

Empty lists mean the account belongs to no organization. That is normal, not an error.

## `select_workspace`

Makes the session work in a workspace, and remembers the choice for the next sessions. Pass `null` to go back to your personal space.

**Permission:** `workspaces:write`. **Credits:** free. **Nodaro Cloud only.**

| Parameter | Type | Notes |
| --- | --- | --- |
| `workspace_id` | string or null | A workspace id from `list_workspaces`, or `null` for your personal space. |

**Returns:** whether the workspace was selected or refused.

- **The server decides.** The tool proposes a workspace, and Nodaro accepts it or refuses it. Only a workspace that was accepted is remembered.
- **The choice is checked at every session.** Membership can end between two sessions. If you are no longer in the saved workspace, Nodaro clears the choice and the session continues in your personal space.
- **Selecting grants nothing.** It records where the session's work belongs. It gives no access and moves no work, so a wrong choice costs one step and exposes nothing.

Usage reports of an organization are not available through MCP. Read them with the SDK, the CLI or the REST API.

## Frequently asked questions

### Why does my assistant not have the workspace tools?

The tools exist only on Nodaro Cloud instances where organizations are switched on. On other instances they are absent, and connections authorized before workspaces existed lack the permissions until you reconnect.

### Does the assistant remember the workspace I chose?

Yes. select_workspace saves the choice for the next sessions, and Nodaro checks it again at the start of every session. If you left the workspace, the session goes back to your personal space.

### How do I go back to my personal space?

Ask the assistant to call select_workspace with workspace_id set to null.