# Set up Signals Corps in an AI tool

Use this guide to connect Codex, Claude Code, or another compatible AI tool to Signals Corps. For the complete experience:

1. connect the remote MCP server for authenticated Control Plane data and hosted actions;
2. install the CLI if the tool must scan a local, private, or uncommitted working tree; and
3. install the Signals Corps plugin when its official distribution is published, so the tool can follow the reviewed scan and triage workflows automatically.

The plugin is the workflow layer. It does not replace MCP authentication, server-side authorization, or the CLI's bounded local-file collection.

## Copyable complete-setup prompt

Paste this into an AI tool that can read web pages and manage its own MCP configuration. A tool with local command access can also offer to install the CLI. It must explain changes and wait for approval before modifying configuration or installing software.

```text
Set up Signals Corps for this AI tool. Connect its MCP client to https://controlplane.signalscorps.com/mcp and use the browser OAuth flow so I can sign in with my Signals Corps account. Do not ask me to copy or paste a bearer token. If you can run local commands, check for Node.js 22.12 or newer and the signalscorps CLI. Before installing the CLI or changing any configuration, show me the exact command or change and wait for my approval. After connecting, list my Workspaces. Do not run a scan until I ask. Never confirm a write action until you have shown me its preview and I explicitly approve it.
```

## 1. Connect the MCP server

The Signals Corps MCP server provides the same bounded Supply Chain reads available in Control Plane plus a small confirmed-action surface. Your Workspace role is enforced for every call.

### Server URL

`https://controlplane.signalscorps.com/mcp`

### Connect

1. Add the server URL to an MCP client that supports remote Streamable HTTP servers and OAuth.
2. The client opens AuthKit in your browser. Sign in with the same account used for the Control Plane.
3. Review and approve the client authorization request.
4. Ask the client to run `list_accessible_workspaces` before selecting a Workspace.

For Codex, add the server from **Settings → MCP servers** and paste the server URL. For another supported client, choose its remote HTTP/OAuth option and use the same URL.

### Verify the connection

Ask the client to list your Workspaces. A successful response from `list_accessible_workspaces` verifies the protocol connection, browser authentication, Signals Corps identity link, and current Workspace membership without starting a scan.

## 2. Install the CLI for local scans

Use the CLI for a local directory, private source, or uncommitted changes. The MCP repository tool accepts only public GitHub repository URLs, and the MCP text tool accepts only bounded JSON or Markdown that is safe to submit. Do not work around those boundaries by sending arbitrary private source through a text tool.

The CLI requires Node.js 22.12 or newer. During Staging it is intentionally not
published to a public registry. From a reviewed Control Plane checkout, review
and approve these local installation commands before an AI tool runs them:

```bash
pnpm install --frozen-lockfile
pnpm --filter @signalscorps/cli build
npm install --global ./apps/supply-chain-cli
```

Authenticate through the browser device flow, then scan a path:

```bash
signalscorps login
signalscorps scan ./path/to/source
```

Use `--workspace wsp_...` when you need to override the active Workspace. The CLI discovers only supported agent files, constructs a bounded archive, uploads it through the private quarantine boundary, and waits for the centrally produced result. It never runs repository code, scripts, hooks, package managers, or builds. Do not ask an AI tool to recreate that archive process itself.

## 3. Install the plugin and skills

The official Signals Corps plugin is not published yet. Until this section contains a Signals Corps-owned marketplace coordinate and pinned release, use the MCP and CLI setup above. Do not install a third-party package merely because it uses the Signals Corps name.

The planned plugin will provide provider-neutral skills for:

- scanning supported agent assets with the correct MCP or CLI path;
- triaging findings without treating incomplete or failed scans as clean; and
- reviewing repository coverage, recent scans, posture, and plan capacity.

Installing the plugin will not grant additional access. MCP calls will continue to enforce the signed-in user's Workspace membership and role, and local scans will continue to use the CLI's browser authentication and bounded upload path.

## How scan requests are routed

- **Local, private, or uncommitted source:** use `signalscorps scan <path>`.
- **Public GitHub repository:** use `prepare_on_demand_repository_scan`, show its preview, and wait for explicit approval before confirmation.
- **Public JSON or Markdown:** use `prepare_on_demand_text_scan` only when the content contains no secrets or private source, then show its preview and wait for explicit approval.
- **Existing GitHub scan:** use `prepare_rerun_scan` to rescan its exact recorded revision, then show its preview and wait for explicit approval.

## Available MCP tools

- list accessible Workspaces;
- read Supply Chain security posture;
- list repositories and monitoring state;
- list scans and retrieve normalized findings;
- search rules and view triggered scans; and
- read plan capacity and hosted-scan usage.

Users with scan permission can prepare bounded on-demand scans and exact-revision scan reruns. Administrators can also prepare Workspace creation, repository monitoring changes, and Workspace invitations. A prepare tool returns a ten-minute preview and digest without making the change. Show that preview to the user, wait for explicit approval, and only then call confirm_action with the exact action ID and digest. Use deny_action to cancel it.

The server cannot change policy, change an existing member's role, delete resources, or modify billing. Repository source, credentials, and inaccessible resource existence are never returned.

## Permissions

Owners and administrators can manage their Workspace. Developers can read product data and run scans, but cannot manage members, billing, integrations, repository monitoring, or Workspace settings. Supplying another Workspace ID does not grant access.

## Sign out or revoke access

Remove the Signals Corps server from the MCP client to delete its local connection. Revoke the client authorization from your Signals Corps authentication settings when available. Signing out of the Control Plane does not silently copy or expose a token to the MCP client.

Run `signalscorps logout` to remove the CLI credential stored for the current operating-system user. Removing the plugin removes its workflow instructions but does not itself revoke an MCP authorization or delete the CLI credential.

## Troubleshooting

- If browser authentication does not open, confirm the client supports remote MCP OAuth and use the exact server URL above.
- If a local scan command is unavailable, confirm Node.js is at least 22.12 and run `signalscorps --help` to verify the CLI installation.
- If the AI tool cannot run local commands, connect MCP in that tool and run local scans from a terminal instead.
- If a Workspace is missing, ask a Workspace administrator to review your membership.
- If authorization was changed, reconnect so the client obtains a fresh session. Server-side membership is checked on every MCP request.
- A generic “unavailable or inaccessible” response intentionally does not reveal whether another Workspace's resource exists.