BigDataCloud MCP integration for AI agents.
Connect AI agents to BigDataCloud through 4 structured actions, including get country by ip, reverse geocode with timezone, and get network by ip. Review aut…
- ACTION CONTRACTS
- 4
- 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 BigDataCloud integration exposes
The BigDataCloud Agent App exposes 4 provider-backed actions for location, security, and data work. Its current contract lets an authorized agent get country-level bigdatacloud geolocation data for an ip address, reverse geocode coordinates and return timezone data from bigdatacloud, and get bigdatacloud network and asn details for an ip address. 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 BigDataCloud account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BigDataCloud capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_country_by_ipREADGet country-level BigDataCloud geolocation data for an IP address.
INPUTS: ip / localityLanguage
reverse_geocode_with_timezoneREVIEWReverse geocode coordinates and return timezone data from BigDataCloud.
INPUTS: latitude / longitude / localityLanguage
get_network_by_ipREADGet BigDataCloud network and ASN details for an IP address.
INPUTS: ip / localityLanguage
get_timezone_by_ipREADGet BigDataCloud timezone data for an IP address.
INPUTS: ip / utcReference
INPUT CONTRACTS
Know what the action needs before it runs.
get_country_by_ip
ipOPTIONAL- Optional IPv4 or IPv6 address to query. If omitted, BigDataCloud uses the connector server IP.
localityLanguageOPTIONAL- Optional ISO 639-1 language code used to localize locality names, or `default` for the first administrative language.
reverse_geocode_with_timezone
latitudeREQUIRED- The latitude coordinate in WGS84 decimal degrees.
longitudeREQUIRED- The longitude coordinate in WGS84 decimal degrees.
localityLanguageOPTIONAL- Optional ISO 639-1 language code used to localize locality names, or `default` for the first administrative language.
get_network_by_ip
ipOPTIONAL- Optional IPv4 or IPv6 address to query. If omitted, BigDataCloud uses the connector server IP.
localityLanguageOPTIONAL- Optional ISO 639-1 language code used to localize locality names, or `default` for the first administrative language.
get_timezone_by_ip
ipOPTIONAL- Optional IPv4 or IPv6 address to query. If omitted, BigDataCloud uses the connector server IP.
utcReferenceOPTIONAL- Optional Unix time reference in seconds used to evaluate timezone and DST state.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Country By Ip
Get country-level BigDataCloud geolocation data for an IP address. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_country_by_ipVerify with Get Network By Ip
Get BigDataCloud network and ASN details for an IP address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_network_by_ipSAFETY BOUNDARY
Operate BigDataCloud with explicit limits
- Authorize BigDataCloud with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BigDataCloud 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 BigDataCloud rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BigDataCloud task completed successfully.
CONNECTION MODEL
API key
BigDataCloud API key passed with the key query parameter. Create your account and get a key here: https://www.bigdatacloud.com/docs/getting-started
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
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 BigDataCloud.