How to connect Foursquare to OpenClaw
Connect Foursquare to OpenClaw with ClawLink: paste your Foursquare key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
FoursquareAPI KEYMCPFoursquare provides location-based search and discovery, offering detailed venue information, place recommendations, and geospatial data for businesses and points of interest worldwide.. Once connected, OpenClaw can read and act on Foursquare from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Foursquare access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Foursquare setup: install one ClawHub skill, connect Foursquare in the browser, and OpenClaw can call real Foursquare actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Foursquare.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Foursquare
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Foursquare?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Foursquare in the ClawLink dashboard — paste your Foursquare API key once.
Verify the connection by asking OpenClaw:
Use Foursquare to autocomplete places and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Foursquare is connected in the dashboard, that agent calls the same 8 Foursquare tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Foursquare MCP for OpenClaw
Looking for a Foursquare MCP server for OpenClaw? ClawLink connects Foursquare to OpenClaw and exposes 8 Foursquare tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Foursquare integration works the same way.
What the OpenClaw Foursquare integration can do
8 Foursquare tools are ready for OpenClaw once the account is connected.
All 8 Foursquare tools for OpenClaw
| Tool | What it does |
|---|---|
Autocomplete places foursquare_autocomplete_places | Returns autocomplete suggestions for places as the user types their search query |
Get trending venues foursquare_get_trending_venues | Retrieves venues currently trending in a specified geographic area, sorted by popularity based |
Retrieve nearby places v3 foursquare_retrieve_nearby_places_v3 | The GetNearbyPlaces endpoint retrieves a list of places near a specified location, primarily |
Retrieve place photos by ID foursquare_retrieve_place_photos_by_id | Retrieves photos associated with a specific place in Foursquare's database |
Retrieve place tips using fsq ID foursquare_retrieve_place_tips_using_fsq_id | Retrieves user-generated tips for a specific place in the Foursquare database |
Retrieve places by ID foursquare_retrieve_places_by_id | Retrieves detailed information about a specific place using its unique Foursquare ID (FSQ ID) |
Search places API request foursquare_search_places_api_request | The GetPlacesSearch endpoint allows you to search for places in the Foursquare database based |
Validate credential foursquare_validate_credential | Validates Foursquare API credentials by performing a lightweight place search |
Try it: find the Foursquare tool you need
Browse the 8 Foursquare tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Foursquare to autocomplete places and walk me through the result in plain English.
Pull the relevant data from Foursquare, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Foursquare, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Foursquare, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Foursquare working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Foursquare API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Foursquare account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Foursquare. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Foursquare actions to the runtime in a format your agent can reliably use. | 8 tools for Foursquare are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Foursquare to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Foursquare in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Foursquare key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Foursquare skill but can't call the tools
The ClawHub skill teaches OpenClaw about Foursquare, but the calls run through the ClawLink plugin and your connected account. Make sure Foursquare is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Foursquare from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Foursquare tools
Foursquare tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Foursquare call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Foursquare returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Foursquare has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Foursquare integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Foursquare: link your Foursquare account once in the browser and OpenClaw can call the Foursquare API through 8 ready-made tools — no custom code or token handling.
How do I add Foursquare to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Foursquare skill from ClawHub, then you click Connect in the dashboard to authorize Foursquare. OpenClaw calls the tools from the next message — no config files, and the Foursquare key you paste is stored server-side instead of in your environment.
How long does it take to connect Foursquare to OpenClaw?
About two minutes. Sign in, click Connect next to Foursquare in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Foursquare up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Foursquare working from chat.
OpenClaw installed the Foursquare skill but can't call the tools
The ClawHub skill teaches OpenClaw about Foursquare, but the calls run through the ClawLink plugin and your connected account. Make sure Foursquare is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
