Skip to content
Public Signal Labs

Setup guide

Connect another app

If your app supports outside research tools, point it at Public Signal.

Connection address (MCP URL)

https://publicsignallabs.com/mcp

This address is public and is not a secret. You never need to open it in a browser: your app pastes it in during setup.

Before you start

For people whose app is not listed in our setup guides and who are comfortable following that app's own settings.

  • Your app must support adding a remote MCP server over HTTPS with browser sign-in (sometimes called OAuth). If it only accepts an API key or a command that runs on your computer, it cannot use this connection address.
  • A Public Signal account whose credits you want to use for research.
  • A computer is recommended: most apps expose server settings on desktop, not on phones.
  • Using the consumer Gemini app? Google's custom-app feature is limited to Gemini Spark, not ordinary Gemini chats. Current requirements include Spark access, age 18+, the US, a personal Google account, English, and Keep Activity turned on. Check Google's linked eligibility guide first; this is not a claim that every Gemini account can connect.

Effort: Varies by app. Take it one step at a time; nothing here runs research or spends credits until you send the first request yourself.

Steps

  1. Confirm your app supports this kind of connection

    Look in your app's settings or help for phrases such as Add MCP server, Remote MCP server, Custom connector, or Connect an app. The setup must accept a server URL and then open a browser to sign in.

    If the app requires a manually supplied API key or bearer token instead of browser sign-in, use Public Signal here instead. Leave optional advanced client-ID and secret fields empty when automatic registration is offered; do not paste a browser-session token.

    You should now see: You have found a settings screen that accepts a remote server URL.

  2. Add Public Signal with the connection address

    Create a new server or connector entry, name it Public Signal, and paste the connection address shown at the top of this guide. Save the entry. You do not need to invent a client ID, secret, or extra headers: apps that support this flow register themselves automatically.

    You should now see: The app lists Public Signal as an added (not yet authorized) server.

  3. Sign in to Public Signal and approve the connection

    The app should open a browser and ask you to sign in to Public Signal. Use the Public Signal account whose credits you want to use, review the access request, and approve it. This lets the app act on your behalf; your password is not shared with the app.

    You should now see: The browser confirms approval and returns you to your app or tells you to go back.

  4. Check the tools, then try one small lookup

    Follow your app's own way of listing or enabling tools and confirm Public Signal appears. Then send the bounded first request from this guide. Running research uses your Public Signal credits, and your app may have its own usage charges.

    You should now see: You receive a short profile summary with a source link, or a clear error to follow.

Your first request

Copy the request below and send it in your app when you are ready. It asks for exactly one profile, so you can confirm the connection without starting a large search. Running it uses Public Signal credits, and your app may have its own usage charges.

First request (copy, then send in your app)

Using Public Signal, look up the public Instagram profile @natgeo. Summarize its bio and follower count, and include its profile link. Use only one profile lookup; do not fetch follower lists or expand the research.

Keep it switched on

  • Some apps need the connection enabled in each conversation; others attach tools automatically. Follow your app's guide to check the current session's tools.
  • If Public Signal does not appear, remove the entry and add it again from step 2 rather than editing the URL by hand.

Next, bring your own campaign brief and ask for a small evidence-backed shortlist. Build your first creator shortlist walks through that.

If something goes wrong

  • My app only asks for an API key: Then it does not support this connection. Public Signal signs you in through a browser instead of issuing keys. Use the hosted agent in your workspace rather than forcing a key into that field.
  • It keeps asking me to sign in: Finish approval in one browser profile, then return to the app. If you authorized the wrong Public Signal account, disconnect and sign in with the account whose credits you want to use.
  • I connected it, but nothing happens: The connection is usually off until you enable it in the current conversation. Open a new conversation, enable Public Signal in the app's tools or connectors menu, and check its tools are listed before retrying.

Still stuck? Get connection help covers the common cases across every app, or write to support@publicsignallabs.com.

Remove the connection

  • Delete the Public Signal entry in the same settings surface where you added it, following your app's own removal steps.
  • Use the app's logout or clear-authentication option where available. Removing configuration alone does not establish that issued credentials are revoked. Contact support if you need help revoking access.

Good to know

  • Signing in lets your app use Public Signal on your behalf. Your Public Signal password is not shared with the app.
  • Research uses your Public Signal credits. Your AI app may have its own plan or usage charges, and hosted-agent chats also consume credits for model inference.
  • Public Signal uses browser sign-in, not API keys or manually pasted access tokens. Use automatic registration where offered; do not invent a client ID or secret.
  • Prefer to skip setup entirely? Open the agent and research here instead.