Skip to main content
The Bridgly MCP server exposes every LinkedIn, X (Twitter), and Reddit endpoint as a Model Context Protocol tool, so an AI client can pull structured social data on its own. It also exposes a billing_get_info tool so the model can read your remaining credit balance. The server speaks Streamable HTTP — the standard transport for remote MCP servers — over a single endpoint: 
https://mcp.bridgly.app/mcp
You authenticate with your Bridgly API key (bgly_…) as a bearer token, exactly like the REST API. Every tool call deducts credits from the account the key belongs to.
Need a key? Create one on the API Keys page of your dashboard. Keep it server-side — anyone with the key can spend your credits.

​
Connect your client

Add the server from the CLI:
claude mcp add --transport http bridgly https://mcp.bridgly.app/mcp \
  --header "Authorization: Bearer bgly_YOUR_KEY"
Then start a session and ask it to pull a profile — the Bridgly tools appear automatically.

​
Available tools

Tools mirror the API’s endpoints one-to-one, named after their path — /x/get-user becomes x_get_user, /linkedin/search/jobs becomes linkedin_search_jobs, and so on. Each tool’s input schema is the endpoint’s request schema, so your client autocompletes every field with its description.

X (Twitter)

x_get_tweet_detail, x_search, x_search_users, x_get_user, x_get_user_tweets, x_get_followers, and more.

Reddit

reddit_get_post, reddit_get_subreddit, reddit_get_user, reddit_list_subreddit_posts, reddit_search_*, and more.

LinkedIn

linkedin_get_profile_from_url, linkedin_get_job, linkedin_search_people, linkedin_search_jobs, and more.
Plus one account tool:
  • billing_get_info — the account’s current spendable credit balance and billing settings. No input required.
Browse the full request and response shape for every tool in the API Reference — each MCP tool takes the same input as its matching endpoint.

​
How results come back

Each call returns the API response as-is — the { timeMs, creditsCost, data } envelope for scrapes, the billing snapshot for billing_get_info — as JSON text the model can read directly. If a call fails, the tool returns the error message (for example, an invalid key or an out-of-credits response) so the model can react instead of silently retrying.

​
Security notes

Stateless by design

Each request is handled in isolation and bound only to the key you send. No session state is shared between callers.

Your key, your credits

Calls are billed to the account the key belongs to. Rotate or revoke a key anytime from the dashboard without affecting your other integrations.