MCP Commands
The cyberstrike mcp commands manage Model Context Protocol servers. There are five subcommands: list, add, auth, logout, and debug.
📸 SCREENSHOT: mcp-commands.png
MCP command interface
Caution
Server config lives in cyberstrike.json (see Local / Remote servers), and servers are managed interactively in the /mcps TUI dialog. There are no mcp status, health, start/stop/restart, remove, config, tools, logs, export/import, install, or update commands.
mcp list
cyberstrike mcp list # alias: lsLists the configured MCP servers.
mcp add
cyberstrike mcp addFully interactive — it prompts for local vs remote, the command or URL, and a name, then tests the connection before saving. It takes no positional name or flags; to script server setup, write the entry into cyberstrike.json directly.
mcp auth
cyberstrike mcp auth [name] # authorize an OAuth servercyberstrike mcp auth list # list OAuth-authorized serversAuthorizes a remote server that uses OAuth (opens the browser if needed). See OAuth.
mcp logout
cyberstrike mcp logout [name]Removes stored OAuth credentials for a server.
mcp debug
cyberstrike mcp debug <name>Inspects a server’s connection — useful when a server fails to load or its tools don’t appear.
Related Documentation
- Bolt / MCP Overview - MCP basics
- Local Servers - Local server config
- Remote Servers - Remote server config
- OAuth - OAuth authentication