Storm query
Run Storm against the Cortex. Results stream in as they arrive.
Step through
Nodes left after each step. Steps run read-only, so nothing is changed.
| Step | Operation | Nodes | Run |
|---|
| Form | Value | Tags | ||
|---|---|---|---|---|
| Run a query to see nodes. | ||||
Tags
Every tag in the Cortex. A tag with a title is part of the taxonomy that lint checks against; tags made on use (like a confidence leaf) have none. Edits go to the selected branch.
Power-Ups
The Storm packages installed in the Cortex: what each adds, where it came from, what it may
do beyond the person running it, and whether it's ready to use. Set a Power-Up's API key here. Admins can also
remove a Power-Up and choose which roles may use it. Packages are installed only by just init, from
powerups/.
| Package | Version | Source | |
|---|---|---|---|
| Loading packages… | |||
Users
Everyone who can sign in, and their role: viewers read, analysts change data, admins also
manage users and Power-Ups. People sign in with an API key you issue here, shown once. The same commands
run from the terminal as just user.
| User | Role | Status | UI key | |
|---|---|---|---|---|
| Loading users… | ||||
Settings
Your account, and how to connect an AI agent to this Cortex over MCP.
Your account
- User
- Role
- Signed in with
Connect an MCP client
An MCP client, such as Claude Code, runs Storm here as an agent account, never as you. An agent reads main but writes only to its own branches, so nothing it adds reaches main until someone reviews and merges it under Agent branches.
- Get an agent key. On the page, Add user with the role Agent, one per person's client or per tool. Its 90-day key is shown once; Issue key rotates it. Ask an admin to add an agent account for you on the Users page. They'll send you its 90-day key, shown to them once.
-
Add this server to your client. In Claude Code, run this with the key in place of
<key>:--scope usermakes it available in every project. Other clients take the URL and header in their config, for example.mcp.json, with the key in theSYNAPSE_MCP_KEYenvironment variable so it never lands in a file you might commit: -
Trust the local certificate. This stack uses a mkcert certificate, so start Claude Code with
On this machine,
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"just mcp-key && just mcp-registerdoes steps 1 and 2 for the built-inagentaccount. -
Check it. In Claude Code,
/mcpshowssynapseas connected. Ask it something like "How many inet:fqdn nodes are in Synapse?"
The agent can read everything in main: don't use it on TLP:RED or TLP:AMBER+STRICT material. Its key expires after 90 days.
Branches
Branch the graph, change it (deletes included), review the diff, check it, then merge into main. Merging stays locked until the latest check passes and nothing has changed since.
| Branch | Changes | Last edit | Check | |
|---|---|---|---|---|
| Loading branches… | ||||
Ran