MCP guide

Connect Codex or Claude Code to SanSignal using your account. Install MCP and the companion skills together once. The connection works across your organizations and projects within your current permissions.

Install

Open Developers → MCP in the dashboard, choose Codex or Claude Code, and copy the command for Linux / macOS or Windows PowerShell. Run it in your terminal, then sign in with SanSignal when prompted. The shell script detects Linux or macOS automatically and requires Python 3 and curl. PowerShell uses its built-in download and JSON support.

The same installation is available directly below. Change codex to claude to use Claude Code.

Linux / macOS:

curl -fsSL 'https://sansignal.com/mcp/install.sh' | sh -s -- --client 'codex' --endpoint 'https://api.sansignal.com/mcp' --environment 'production' --source 'https://sansignal.com/mcp/skills.json'

Windows PowerShell:

& {
  $ErrorActionPreference = 'Stop'
  $ssResponse = Invoke-WebRequest -UseBasicParsing 'https://sansignal.com/mcp/install.ps1'
  $ssScript = if ($ssResponse.Content -is [byte[]]) { [Text.Encoding]::UTF8.GetString($ssResponse.Content) } else { [string]$ssResponse.Content }
  & ([ScriptBlock]::Create($ssScript)) -Client 'codex' -Endpoint 'https://api.sansignal.com/mcp' -Environment 'production' -Source 'https://sansignal.com/mcp/skills.json'
}

Install the selected client first. The command adds a user-level connection named sansignal and installs the SanSignal skills in your personal skills directory. Existing connections with a different URL or authentication settings and locally edited skills are preserved. Running the command again updates installer-managed skills and reconnects the same account connection. For Codex, browser authorization starts from the installer. For Claude Code, open the client, run /mcp, and sign in to sansignal. Restart the client if newly installed skills do not appear.

For local development, copy the dashboard’s command: it uses the configured local API endpoint and website, with a separate sansignal-local connection. The default local endpoint is http://localhost:3618/mcp, and installer assets are served by make dev:website at http://localhost:3611. There is no per-project installation.

Choose a project

Ask your agent to list your SanSignal projects. The list_projects tool returns enabled projects you can access across organizations. Select a project, then use its project_id with get_project_context and every other tool. An agent should confirm the intended project when your request is ambiguous.

Project access remains live: changing your membership or resource permissions affects the next call. A dashboard-only grant does not become unrestricted instrument access. Project IDs, resource IDs, cursors and preview handles cannot bypass these checks.

Full project administrators and platform administrators can open the MCP page and change Enable MCP for this project. Turning it off hides that project from list_projects and blocks MCP operations for it. Other projects and the user’s connection continue to work. Re-enabling the project makes it available again to users who have access.

Account access

OAuth authorization belongs to your SanSignal user and client at the API’s single /mcp endpoint. The client requests the permissions advertised by your deployment. Review them during browser consent; diagnostics and writes require their corresponding OAuth permission and current project permissions. Deployment and organization policy still apply. You can review and disconnect authorizations in Connected AI apps in your account. Disconnecting invalidates the authorization for every project; deleting local MCP configuration alone does not revoke server-side access.

Existing project-specific MCP connections must be removed and installed again with the account endpoint. Legacy project credentials are invalidated during the migration; they are never silently upgraded to wider access.

If a project is missing, check project membership, organization status and its MCP enable setting. For an expired authorization, sign in again. If a tool reports a permission error, check access before retrying. See the MCP tool reference for arguments, limits and errors.

MCP uses your account for interactive agent workflows. Application integrations continue to use the separate Developer API and ingestion credentials. Skills contain guidance and references; they do not grant access or store credentials.