Bright Data MCP integration for AI agents.
Connect AI agents to Bright Data through 6 structured actions, including get account status, get dataset metadata, and get snapshot metadata. Review authenti…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bright Data integration exposes
The Bright Data Agent App exposes 6 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent fetch the bright data account status for the connected api key and return account request capability metadata, fetch bright data marketplace dataset field metadata for a dataset id, and fetch metadata for a bright data marketplace dataset snapshot. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bright Data account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bright Data capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_statusREADFetch the Bright Data account status for the connected API key and return account request capability metadata.
get_dataset_metadataREADFetch Bright Data marketplace dataset field metadata for a dataset ID.
INPUTS: datasetId
get_snapshot_metadataREADFetch metadata for a Bright Data marketplace dataset snapshot.
INPUTS: snapshotId
get_snapshot_partsREADFetch the number of delivery parts for a ready Bright Data marketplace dataset snapshot.
INPUTS: snapshotId / format / compress / batchSize
list_dataset_viewsREADList Bright Data dataset views available to the connected account.
list_datasetsREADList Bright Data marketplace dataset IDs available to the connected account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_dataset_metadata
datasetIdREQUIRED- The Bright Data dataset identifier.
get_snapshot_metadata
snapshotIdREQUIRED- The Bright Data snapshot identifier.
get_snapshot_parts
snapshotIdREQUIRED- The Bright Data snapshot identifier.
formatOPTIONAL- The snapshot delivery format.
compressOPTIONAL- Whether the corresponding snapshot download uses gzip compression.
batchSizeOPTIONAL- The record count used for each response batch.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Status
Fetch the Bright Data account status for the connected API key and return account request capability metadata. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_statusVerify with Get Dataset Metadata
Fetch Bright Data marketplace dataset field metadata for a dataset ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_dataset_metadataSAFETY BOUNDARY
Operate Bright Data with explicit limits
- Authorize Bright Data with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Bright Data data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bright Data rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bright Data task completed successfully.
CONNECTION MODEL
API key
Bright Data API key sent as a Bearer token in the Authorization header. Create or manage API keys from Bright Data account settings: https://brightdata.com/cp/setting/users.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bright Data.