Reference

Keeping it current

One update keeps the installed helper and managed editor integration current; targeted repair and verification remain available when you need them.

Run the managed update

Terminal
contextstream-mcp update            # to the latest
contextstream-mcp update --check    # just tell me if there's one

The hosted MCP service is updated by ContextStream; there is no server for you to reinstall inside each editor. The first command maintains the part on your machine. It:

  • installs a newer Rust helper when one is available;
  • keeps already configured editors on the current hosted connection;
  • refreshes their supported lifecycle hooks;
  • refreshes their global managed instructions; and
  • refreshes this project's managed instructions when you run it from a linked project.

That editor refresh still runs when the binary is already current. It is limited to editors you previously selected, so an unattended update does not enroll a newly detected editor on its own. --check only reports whether a new binary is available and does not perform the refresh.

You normally stop there. If one refresh step reports a warning, use contextstream-mcp doctor to identify that layer and then run the matching repair command below.

Verify the whole connection

Terminal
contextstream-mcp doctor

Reports what's actually configured per editor, with evidence, and offers to repair only the parts it manages. It won't touch configuration you wrote yourself.

Repair or preview one layer

CommandWhat it refreshesEffective scope
update-rulesManaged blocks in instruction filesGlobal, project, or both
update-configsManaged MCP connection entriesGlobal, project, or both where the editor supports them
update-hooksSupported editor lifecycle hooksGlobal hook files

Use these when doctor identifies one stale layer, when you want to preview a managed rewrite, or when you deliberately changed one part of the setup. They accept the same targeting flags:

Terminal
--scope global|project|all      # which layer
--editors <ids>                 # only these editors
--only-configured               # skip editors you haven't set up
--dry-run                       # show the changes, write nothing

For update-hooks, project scope is currently ignored because the managed hook files are global; the command reports that rather than pretending it wrote a project hook. --dry-run shows the intended managed changes without writing them.

Changing your setup

Terminal
contextstream-mcp configure                  # interactive menu
contextstream-mcp configure --list-options   # what can be set

The menu covers editors, transcripts, API key, workspace, hooks, rules, and connection files.

Removing it

Terminal
contextstream-mcp uninstall
contextstream-mcp uninstall --scope all --git-hooks

Removes the hooks, connection entries, and rules it added. Your workspace and its memory are untouched — this uninstalls the local integration, not your data.

If it doesn't work

update says the binary is current but an editor is stale. The managed refresh still ran; read its warnings, then run doctor and the named repair. Use contextstream-mcp update --force only when the binary itself needs reinstalling.

doctor reports an editor I don't use. It detected an install. Use --editors to narrow what the maintenance commands touch.

Regenerating overwrote my rules. Only the marked generated block is replaced. Anything outside it is preserved — move your rules out of that block.

Next