Before you start
First follow Set up MCP access to check Business or Agency eligibility, copy the correct address and review permissions. These recipes reflect client documentation. Additional clients have not all been individually tested with Signal & Science; verify a harmless read before relying on one.
Claude Code
Run the command below with the connect address copied from Signal & Science in place of URL_FROM_SETTINGS. Complete the browser sign-in when Claude Code requests authentication.
claude mcp add --transport http signal-science URL_FROM_SETTINGS
Codex
Replace URL_FROM_SETTINGS with the connect address copied from Signal & Science. Add the remote server, then authorize it. Codex clients that share this MCP configuration can use the connection, subject to their own tool controls.
codex mcp add signal-science --url URL_FROM_SETTINGS codex mcp login signal-science
Gemini CLI
Add a remote HTTP server using the connect address from Signal & Science. In Gemini CLI, run /mcp auth signal-science if authentication is required. The CLI can discover OAuth settings and open a browser for sign-in.
gemini mcp add --transport http signal-science URL_FROM_SETTINGS
Gemini Code Assist
Use agent mode and configure a remote MCP server in the Gemini settings. For the token path, follow Access tokens: use the token connector address as httpUrl and supply an Authorization header containing Bearer followed by your scoped token. Follow your Code Assist version's MCP configuration requirements.
Keep the token entry in private user-level configuration, not a project or workspace file that may be committed or shared. Use the client's environment-variable or secret-store support when available. Never commit a populated Authorization header to version control.
Cursor
Open Cursor's MCP settings and add a remote server with the connect address from Signal & Science. For a manual configuration, add a named entry under mcpServers with the address as url. Connect the server and complete the OAuth sign-in. Enable its tools for the agent you use.
GitHub Copilot in VS Code
In VS Code, run MCP: Add Server from the Command Palette and choose an HTTP server. Paste the connect address from Signal & Science, save the configuration and follow the authentication prompt. Review server trust and tool approval separately. This recipe covers Copilot in VS Code; other Copilot surfaces have different MCP capabilities.
GitHub Copilot CLI
Use the CLI's MCP controls to add a remote HTTP server with the connect address from Signal & Science. Enable it and use /mcp auth with the server name to start or repeat browser authorization. Verify that its tools are available in your CLI session. Do not assume the same configuration works in Copilot cloud agent or code review.
OpenCode
In opencode.json, add a named server under mcp with type set to remote and url set to the connect address from Signal & Science. OpenCode can discover OAuth automatically. If needed, run opencode mcp auth with that server name and complete browser sign-in.
Cline CLI
Run cline mcp to open the MCP wizard. Add a remote HTTP server with the connect address from Signal & Science, enable it, then choose Authorize OAuth. This recipe covers the CLI; the extension may have different setup controls.
Kiro
Add a remote MCP server in Kiro's MCP configuration, using the connect address from Signal & Science as url. Complete the OAuth sign-in. With no pre-registered client ID, Kiro can use dynamic client registration. Use the configuration location and authorization controls for your IDE or CLI version.
Verify access
Check and manage the connection: ask which workspaces the client can access, then request a read of the current plan without making changes. Check the workspace and permissions in Signal & Science. Revoke the connection or token when it is no longer needed.