Skip to main content
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.
If your client asks for a header or a config file instead of opening a sign-in page, connect with an API key.

​
Connect your client

1

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.
2

Sign in and approve

Choose Connect. A Bridgly page opens in your browser. Sign in, or create an account, then allow access.
3

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.

​
What a connected app can do

A connected app acts on the account you signed in with. Scraping tools follow the same credit rules 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

The client may not support OAuth for remote MCP servers, or it may be waiting for a header. Connect with an API key instead.
Leave both empty. The client identifies itself to Bridgly on its own. If it will not continue without them, connect with an API key.
Access may have been removed or may have expired while the client was offline. Reconnect the server in the client and approve access again.
The account you signed in with has run out of credits. Add credits from your dashboard, then retry.