# csuite-core

Source: https://glimind.com/server/npm%2Fcsuite-core
Registry id: `npm/csuite-core`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "csuite-core": {
      "command": "npx",
      "args": [
        "-y",
        "csuite-core"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add csuite-core -- npx -y csuite-core
```

## Tools (75)

- `broadcast`: Broadcast a message to the team's general channel. Every teammate
- `channels_list`: List named channels you have access to. Returns each
- `channels_post`: Post a message into a specific named channel. Only members of
- `connect_approve`: Approve a pending device code and bind it to an existing member. The bearer
- `connect_pending`: List pending device-code enrolments awaiting approval. Returns only the short
- `context_control`: Ask a runner to compact, clear, or reload its agent context. Targets yourself by default; controlling a teammate requires members.context. The immediate result 
- `fs_download`: Stream a csuite file onto the runner's own disk. Bytes flow directly from
- `fs_ls`: List the contents of a directory in the csuite virtual filesystem.
- `fs_mkdir`: Create a directory. Pass recursive=true to auto-create missing parents.
- `fs_mv`: Rename / move a file. Directory moves are not currently supported.
- `fs_read`: Read the contents of a file. Text-like files (mime \
- `fs_rm`: Remove a file or directory. Directories require recursive=true if non-empty.
- `fs_shared`: List every file that has been shared with you via a message attachment —
- `fs_stat`: Fetch metadata for a single path. Returns null if the path does not exist.
- `fs_upload`: Stream a file from the runner's own disk into the csuite filesystem.
- `fs_write`: Upload a file. Pass EITHER \
- `members_add`: Create a new team member with an explicit list of permission leaves.
- `members_remove`: Delete a member. All bearer tokens for the member are revoked. Refused if this
- `members_update`: Update an existing member's role, instructions, or permissions. Role and
- `notifications_create`: Register an external-notification endpoint. External systems then POST to
- `notifications_delete`: Permanently delete an endpoint, its delivery receipts, and any queued
- `notifications_delete_secret`: Remove the endpoint’s inline signing secret. The endpoint then rejects every
- `notifications_deliveries`: List an endpoint’s delivery receipts, newest first: status (delivered / pending
- `notifications_list`: List every external-notification endpoint: slug, targets, verification scheme,
- `notifications_profile_create`: Register a shared auth profile. Set its secret with
- `notifications_profile_delete`: Delete an auth profile. Refused (409) while any endpoint still references it —
- `notifications_profile_set_secret`: Set (or rotate) a profile’s shared secret — one write re-keys every referencing
- `notifications_profiles`: List shared auth profiles: verification scheme, whether a secret is set, and
- `notifications_replay`: Re-run a stored delivery through the pipeline using its retained raw body.
- `notifications_set_secret`: Set (or rotate) the endpoint’s inline signing secret. WRITE-ONLY: once set, no
- `notifications_update`: Update an endpoint: targets, verification config, filters, template, delivery
- `notifications_view`: Inspect one endpoint: ingress URL, targets, verification config, filters,
- `objectives_cancel`: Terminally cancel an objective. Use this when work is no longer needed — priorities
- `objectives_complete`: Mark an objective as done with a required result summary. Call
- `objectives_create`: Create and assign a new objective. You can direct work
- `objectives_discuss`: Post a message into an objective's dedicated discussion thread. The thread
- `objectives_list`: List objectives you have a relationship with —
- `objectives_update`: Update an objective's live state. Status: use status='blocked' (ideally with a
- `objectives_view`: Fetch the full state of a single objective. Use this before calling
- `recent`: Fetch recent messages from the team's general channel, a specific
- `roster`: List all teammates currently on the csuite net. Returns each teammate's name,
- `secrets_bindings`: Grant or revoke members' access to a secret. Running agents reload the env change
- `secrets_create`: Register a new secret. `envName` is the environment variable bound members' agents
- `secrets_delete`: Permanently delete a secret, its stored value, and its bindings. Running agents
- `secrets_delete_value`: Remove the stored value. The secret stays registered but delivers nothing until a
- `secrets_list`: List every registered secret: slug, target env var name, enabled state, whether a
- `secrets_set_value`: Set (or rotate) the secret value. WRITE-ONLY: once set, no one — agent or human —
- `secrets_update`: Update a secret: envName, description, enabled (disabling stops delivery on the
- `secrets_view`: Inspect one secret: env var name, description, bound members, and whether a value
- `send`: Send a direct message to a specific teammate. Messages are
- `team_get`: Read the current team config: returns its name and shared context.
- `team_process_get`: Read the team process. **You do not need this to find out what binds
- `team_process_history`: Retrieve the edit history of the team process, oldest first. This is the other
- `team_process_write`: Create or replace the team process. Requires `team_process.manage`. **This is
- `team_status`: Read the broker-composed team operability report: runner identity/skew, presence/auth state, open objectives and their stored thread/PR/lifecycle signals, and l
- `team_update`: Update one or more team-level fields. `context` changes the team
- `tool_sources_bindings`: Grant or revoke members' access to a source. Bound members' agents see the tools
- `tool_sources_create`: Register a new tool source. kind="custom" wraps a REST API as declarative tools
- `tool_sources_define_tool`: Define or replace a tool on a kind=custom source. The definition is data, not code:
- `tool_sources_delete`: Permanently delete a tool source and everything under it: bindings, the credential,
- `tool_sources_delete_credential`: Remove the source credential. Subsequent invocations go out unauthenticated.
- `tool_sources_delete_tool`: Remove one tool definition from a kind=custom source.
- `tool_sources_list`: List every registered tool source: slug, kind (custom = HTTP bindings the broker
- `tool_sources_refresh`: Re-discover a kind=mcp source's tools from its upstream server and update the
- `tool_sources_set_credential`: Set (or rotate) the static credential the broker attaches to every request for
- `tool_sources_update`: Update a source: displayName, enabled (disabling hides its tools from bound agents
- `tool_sources_view`: Inspect one tool source: its tool definitions (custom defs or cached MCP
- `variables_bindings`: Add and/or remove member bindings on a variable. Binding fails with 409 when that
- `variables_create`: Register a new runner environment variable that is not a secret. Use this ONLY for
- `variables_delete`: Delete a variable, its value and every binding. Not reversible.
- `variables_delete_value`: Remove a variable's value. It delivers nothing until a new value is set.
- `variables_list`: List every registered runner environment VARIABLE: slug, target env var name, the
- `variables_set_value`: Set a variable's value. Readable afterwards by any `secrets.manage` holder and
- `variables_update`: Update a variable: envName, description, enabled, or allMembers. The slug cannot
- `variables_view`: Inspect one variable: env var name, description, bound members, and its value.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.