SwitchSignal

OSS Local Kit and Hosted MCP

Two developer paths: local-first OSS and hosted MCP for paid workspaces.

Use the OSS Local Kit to inspect and run the core evidence workflow without paying for the hosted service. Use Hosted MCP when external agents need to operate inside your SwitchSignal account with identity, entitlement, usage, and audit controls.

Public endpoints

github.com/cliwant/switchsignal-ossgithub.com/cliwant/switchsignal-mcpHosted /mcp.jsonhttps://switchsignal.grindworks.ai/api/mcp

No hosted account required

Open Source Local Kit

Clone the public repo and run category audits, capture plans, signal creation, and campaign-pack generation locally. Bring your own LLM provider or use deterministic output. The sample memo shows the proof table, client decision, quality score, and execution checklist before you install anything.

git clone https://github.com/cliwant/switchsignal-oss.git
cd switchsignal-oss
npm install
npm run demo
npm run pack -- --fixture examples/signals/mailerlite-free-tier.json --provider deterministic
Open cliwant/switchsignal-ossView sample memo

Requires SwitchSignal account and MCP key

Hosted MCP Connector

Install the bridge when Claude, Codex, Gemini-style clients, or custom agents need to call your hosted SwitchSignal workspace with service-side policy enforcement.

{
  "mcpServers": {
    "switchsignal": {
      "command": "npx",
      "args": ["-y", "github:cliwant/switchsignal-mcp"],
      "env": {
        "SWITCHSIGNAL_MCP_KEY": "<SWITCHSIGNAL_MCP_KEY>"
      }
    }
  }
}
Open cliwant/switchsignal-mcp

1. Choose the right path

Use the OSS Local Kit when you want to run the evidence engine locally without a SwitchSignal account. Use Hosted MCP when an external agent needs to operate inside your paid SwitchSignal workspace.

2. Run local OSS or create an MCP key

The OSS kit works with deterministic generation, OpenRouter, Ollama, LM Studio, or any OpenAI-compatible model. Hosted MCP requires a user-scoped key created inside SwitchSignal Settings.

3. Inspect the contract

OSS commands write local files only. Hosted MCP calls read /mcp.json and switchsignal://tool-contracts, then enforce scopes, entitlement, metering, rate limits, and audit logs.

Hosted MCP setup

1. Create a scoped MCP key

Sign in to SwitchSignal, open Settings, and create a user-scoped MCP key. Use read-only scope for discovery, then add write scopes only when the agent needs to create owned watchlists, signals, or packs.

2. Install the hosted connector

Use the public bridge from the cliwant org repo. The bridge stores no key, prints no secret, and forwards local stdio JSON-RPC to the hosted Streamable HTTP endpoint.

3. Inspect the contract

Read /mcp.json and switchsignal://tool-contracts before calling write tools. Every call is scoped, entitlement checked, metered, rate limited, and audit logged.

{
  "mcpServers": {
    "switchsignal": {
      "command": "npx",
      "args": ["-y", "github:cliwant/switchsignal-mcp"],
      "env": {
        "SWITCHSIGNAL_MCP_KEY": "<SWITCHSIGNAL_MCP_KEY>"
      }
    }
  }
}

The bridge can also target local development by setting `SWITCHSIGNAL_MCP_URL=http://localhost:3000/api/mcp`.

Public/private boundary

OSS: local evidence data, audits, capture planning, signal generation, deterministic packs, examples, and tests.

Hosted MCP: agent calls into user-owned SwitchSignal workspaces through scoped keys, entitlement, metering, rate limits, and audit logs.

Hosted product: accounts, billing, recurring capture, private snapshots, campaign generation, client reports, usage, and audit logs.

Private: customer data, production credentials, billing rows, private snapshots, lead lists, and operator-only workflows.

Open MCP repoRead manifest