Foursquare MCP integration for AI agents.
Connect AI agents to Foursquare through 5 structured actions, including get nearby places, get place, and get place photos. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 5
- 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 Foursquare integration exposes
The Foursquare Agent App exposes 5 provider-backed actions for location and data work. Its current contract lets an authorized agent retrieve nearby places around a latitude and longitude with foursquare, retrieve one place by foursquare place id, and retrieve photos for one foursquare place. 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 Foursquare account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Foursquare capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_nearby_placesREADRetrieve nearby places around a latitude and longitude with Foursquare.
INPUTS: latitude / longitude / hacc / altitude / limit
get_placeREADRetrieve one place by Foursquare place ID.
INPUTS: fsqId / fields
get_place_photosREADRetrieve photos for one Foursquare place.
INPUTS: fsqId / sort / limit / classifications
get_place_tipsREADRetrieve tips for one Foursquare place.
INPUTS: fsqId / sort / limit / fields
search_placesREADSearch for places with the Foursquare Places Search endpoint.
INPUTS: query / near / latitude / longitude / radius
INPUT CONTRACTS
Know what the action needs before it runs.
get_nearby_places
latitudeREQUIRED- The latitude coordinate in decimal degrees.
longitudeREQUIRED- The longitude coordinate in decimal degrees.
haccOPTIONAL- The horizontal accuracy radius in meters.
altitudeOPTIONAL- The altitude in meters.
limitOPTIONAL- The maximum number of nearby places to return.
get_place
fsqIdREQUIRED- The unique Foursquare place identifier.
fieldsOPTIONAL- The Foursquare response fields to request.
get_place_photos
fsqIdREQUIRED- The unique Foursquare place identifier.
sortOPTIONAL- The ordering applied to photos or tips.
limitOPTIONAL- The maximum number of photos to return.
classificationsOPTIONAL- The photo classifications used to filter the response.
get_place_tips
fsqIdREQUIRED- The unique Foursquare place identifier.
sortOPTIONAL- The ordering applied to photos or tips.
limitOPTIONAL- The maximum number of tips to return.
fieldsOPTIONAL- The Foursquare response fields to request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Nearby Places
Retrieve nearby places around a latitude and longitude with Foursquare. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_nearby_placesVerify with Get Place
Retrieve one place by Foursquare place ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_placeSAFETY BOUNDARY
Operate Foursquare with explicit limits
- Authorize Foursquare with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Foursquare 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 Foursquare rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Foursquare task completed successfully.
CONNECTION MODEL
API key
Foursquare Places API key used with the Authorization: fsq3 <api_key> header. Generate or revoke it from your project API Keys page: https://docs.foursquare.com/developer/docs/manage-api-keys
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
- 5
- 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 Foursquare.