# How to connect Foursquare to Hermes Agent (paste one key, 8 tools) > Connect Foursquare to Hermes with ClawLink: paste your Foursquare key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/foursquare Most guides for giving Hermes Agent Foursquare access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Foursquare setup: pair once in the browser and your always-on Hermes agent can act on Foursquare for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Foursquare. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Foursquare** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect foursquare # connect Foursquare (browser OAuth) npx -y @useclawlink/cli actions foursquare # list available actions npx -y @useclawlink/cli run foursquare --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Foursquare in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Foursquare API key once. Verify the connection by asking Hermes: > Use Foursquare to autocomplete places and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Foursquare MCP for Hermes Looking for a Foursquare MCP server for Hermes Agent? ClawLink connects Foursquare to Hermes Agent and exposes 8 Foursquare tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Foursquare integration](https://claw-link.dev/openclaw/foursquare) works the same way. ## What the Hermes Agent Foursquare integration can do 8 Foursquare tools are ready for Hermes Agent once the account is connected. ### All 8 Foursquare tools for Hermes | 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 | ## Example prompts **Autocomplete Places** > Use Foursquare to autocomplete places and walk me through the result in plain English. **Get Trending Venues** > Pull the relevant data from Foursquare, summarize it in plain English, and point out anything that needs attention. **Retrieve Nearby Places V3** > Pull the relevant data from Foursquare, summarize it in plain English, and point out anything that needs attention. **Retrieve Place Photos By Id** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Foursquare Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Foursquare integration? Yes. ClawLink is the fastest way to connect Hermes to Foursquare: link your Foursquare account once in the browser and Hermes Agent can call the Foursquare API through 8 ready-made tools — no custom code or token handling. ### How do I connect Foursquare to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Foursquare in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Foursquare in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Foursquare working from chat. ### Hermes paired but still can't use Foursquare Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Hermes PostHog integration](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase tools](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.