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.
Zed
In Zed settings, add a named entry under context_servers with url set to the connect address from Signal & Science. Leave the Authorization header unset for the OAuth path. Zed prompts for sign-in when the remote server requires it.
Roo Code
Follow Access tokens. In the MCP configuration, add a named server with type set to streamable-http and url set to the token connector address. Under headers, set Authorization to Bearer followed by your scoped token. Keep automatic tool approvals limited to actions you intend.
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.
Cascade
Current Windsurf Cascade documentation is published under Devin Desktop. In Cascade's MCP settings, add a remote HTTP server with the connect address from Signal & Science and complete OAuth sign-in. Manual configuration uses a named mcpServers entry with serverUrl. Check the documentation for the product version installed on your computer.
Goose
Open extension configuration and add a Remote Extension using Streamable HTTP. Enter the connect address from Signal & Science. Follow OAuth sign-in, then enable the extension for the session you intend to use.
LibreChat
An administrator configures a remote MCP server with type set to streamable-http and url set to the connect address from Signal & Science. Each user then connects and completes their own OAuth sign-in. Keep a separate authorization for each user rather than sharing a token between users.
LM Studio
Follow Access tokens. Open the MCP configuration and add a named mcpServers entry with url set to the token connector address. Under headers, set Authorization to Bearer followed by your scoped token. Select a model with tool-use support and verify a harmless read.
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.
Continue
Follow Access tokens. In the MCP configuration, use type streamable-http and set url to the token connector address. Under requestOptions.headers, set Authorization to Bearer followed by your scoped token. Enable the server for agent mode and check its tools before use.
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.
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.