Integration

Foursquare integration

Location data and places API for discovering venues, businesses, and points of interest. Search places, get venue details, photos, tips, and check-in data. Essential for location-based apps, local search, venue discovery, and mapping applications.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Foursquare.Built from the 8 Foursquare tools below, on the connection you add once.

Common Foursquare use cases

  • search UI
  • check-in apps
  • venue display
  • review display
  • data enrichment
  • place discovery
  • venue galleries
  • category filtering
  • typeahead
  • local search

What you can do with Foursquare

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Place, 4 operations

  • get_placeGet placeGETRetrieves detailed information about a place including hours, ratings, and contact info.
  • match_placesMatch placesGETFinds the Foursquare place that matches a given name and location.
  • nearby_placesNearby placesGETDiscovers places in the immediate vicinity of a location using Snap to Place technology.
  • search_placesSearch placesGETSearches for places near a location with filtering by category, query, and open status.

Autocomplete, 1 operation

  • autocompleteAutocompleteGETProvides typeahead suggestions for place names, addresses, and search queries.

Category, 1 operation

  • get_categoriesGet categoriesGETRetrieves the complete Foursquare category taxonomy for places.

Photo, 1 operation

  • get_place_photosGet place photosGETRetrieves photos of a place with metadata and various size options.

Tip, 1 operation

  • get_place_tipsGet place tipsGETRetrieves user tips and reviews for a place.

Foursquare API rate limits

  • 50,000 requests per day

Rate limits vary by plan

These are the limits Foursquare documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Foursquare documentation for current values.

Use Foursquare from Claude Code, Cursor or Codex

Connect Foursquare in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Foursquare operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Foursquare

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Foursquare once

    Add your Foursquare connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Foursquare integration FAQ

What can you do with the Foursquare integration?

LiveContext exposes 8 operations on Foursquare, covering place, autocomplete, category and photo. Common uses include search UI, check-in apps and venue display.

What are the Foursquare API rate limits?

Foursquare documents 50,000 requests per day. Rate limits vary by plan Limits are set by Foursquare and can depend on your plan.

Popular integrations

Browse the whole catalog