> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bridgly.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in with your account

> Connect an AI client to the Bridgly MCP server by signing in, with no API key to copy.

AI clients that support OAuth can connect to the Bridgly MCP server with your
Bridgly account. You add the server URL, sign in once in your browser, and
approve access. There is no API key to create, paste, or store in a config file.

```
https://mcp.bridgly.app/mcp
```

<Note>
  If your client asks for a header or a config file instead of opening a sign-in
  page, [connect with an API key](/mcp/connect#connect-with-an-api-key).
</Note>

## Connect your client

<Tabs>
  <Tab title="Claude">
    <Steps>
      <Step title="Add the connector">
        Open **Settings → Connectors** and choose **Add custom connector**.
        Enter a name such as `Bridgly` and the URL `https://mcp.bridgly.app/mcp`.
        Leave the client ID and client secret fields empty.
      </Step>

      <Step title="Sign in and approve">
        Choose **Connect**. A Bridgly page opens in your browser. Sign in, or
        create an account, then allow access.
      </Step>

      <Step title="Use the tools">
        You are sent back to Claude. Enable Bridgly in a chat's tools menu and
        ask for a public profile, a post, or a search.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Code">
    <Steps>
      <Step title="Add the server">
        Add the server without a header:

        ```bash theme={"dark"}
        claude mcp add --transport http bridgly https://mcp.bridgly.app/mcp
        ```
      </Step>

      <Step title="Sign in and approve">
        Start a session, run `/mcp`, select **bridgly**, and choose to
        authenticate. A Bridgly page opens in your browser. Sign in, then allow
        access.
      </Step>

      <Step title="Use the tools">
        Return to your terminal. The Bridgly tools are available in the session.
      </Step>
    </Steps>
  </Tab>

  <Tab title="ChatGPT">
    <Steps>
      <Step title="Add the connector">
        In ChatGPT's connector settings, create a new connector and enter
        `https://mcp.bridgly.app/mcp` as the MCP server URL. Choose **OAuth** as
        the authentication method.
      </Step>

      <Step title="Sign in and approve">
        Choose **Connect**. A Bridgly page opens in your browser. Sign in, or
        create an account, then allow access.
      </Step>

      <Step title="Use the tools">
        You are sent back to ChatGPT. Select Bridgly in a chat and ask for a
        public profile, a post, or a search.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Other clients">
    Add `https://mcp.bridgly.app/mcp` as a remote MCP server and leave the
    authentication fields empty. A client that supports OAuth opens the Bridgly
    sign-in page the first time it connects.
  </Tab>
</Tabs>

## What a connected app can do

A connected app acts on the account you signed in with.

| The app can | The app cannot |
| - | - |
| Look up public data with the scraping tools | Buy credits |
| Read your credit balance and billing settings | Change your billing settings |
| | Create, list, or revoke API keys |

Scraping tools follow the same [credit rules](/responses#credits) as their
matching API endpoints and spend the balance of the account you signed in with.
Checking your balance with `billing_get_info` does not consume credits.

## Stay connected

You sign in once per client. The client renews its access in the background, so
you are not asked to sign in again during normal use. If a client reports that
its access is no longer valid, reconnect it and approve access again.

## Disconnect an app

Remove or disconnect Bridgly in the app's own connector settings. In Claude
Code, run `claude mcp remove bridgly`.

## Troubleshooting

<AccordionGroup>
  <Accordion title="No sign-in page opens">
    The client may not support OAuth for remote MCP servers, or it may be
    waiting for a header. [Connect with an API
    key](/mcp/connect#connect-with-an-api-key) instead.
  </Accordion>

  <Accordion title="The client asks for a client ID or secret">
    Leave both empty. The client identifies itself to Bridgly on its own. If it
    will not continue without them, connect with an API key.
  </Accordion>

  <Accordion title="Tools fail after working before">
    Access may have been removed or may have expired while the client was
    offline. Reconnect the server in the client and approve access again.
  </Accordion>

  <Accordion title="A tool says you have insufficient credits">
    The account you signed in with has run out of credits. Add credits from your
    [dashboard](https://bridgly.app/dashboard), then retry.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.