# Check your installation

Distinguish the installed executable, MCP preflight and workspace admission.

Check the executable and the door separately. A successful local preflight does not grant access to workspace records.

## Identify the executable

Print the version and source commit of the executable.

```text
cambium --version
```



The version includes the executable's source commit. Keep it with the server address when reporting a fault. An adjacent receipt must also match the executable's digest before it can identify those bytes.

## Check the seat package

Check the installed MCP executable, fonts and native canvas without signing in.

```text
cambium mcp --check
```



The preflight checks the packaged fonts and native canvas without signing in. In the host, initialise the MCP server and request its tool list. Use the [plugin guide](/cambium/plugin/) for the correct launcher and environment.

## Check admission

Read the schema, then ask for the intended resource. A roster refusal naming the workspace read action needs a grant from an authorised holder. Changing the executable path or repeating sign-in does not supply that grant.

## Follow a live change

Confirm that the host supports the server's channel protocol and has enabled the plugin's channel. Read the record a notification names before acknowledging it. [Notifications](/cambium/operations/notifications/) describes that distinction.