Foursquare MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_usersB | List all registered Foursquare usernames. |
| add_userC | Register a new user's Foursquare OAuth token. |
| remove_userC | Remove a registered user. |
| get_user_detailsB | Get Foursquare profile for a registered user. |
| get_user_checkinsC | Get checkins for a registered user within an optional date range. |
| get_venue_detailsA | Get full venue details (address, categories, URL, etc.) by venue ID. |
| get_checkin_detailB | Get full detail for a single checkin by ID (includes comments, photos, overlaps, etc.). |
| get_user_venue_historyA | Get unique venues a user has visited, with visit counts and last-visit timestamps. |
| get_user_mayorshipsB | Get a user's current mayorships (venues where they're the mayor). |
| get_user_listsA | Get all lists for a user (saved places, created lists, followed lists). |
| get_list_detailA | Get full detail for a specific list including all venue items. List IDs come from get_user_lists. |
| get_user_tastesB | Get a user's taste preferences (food types, experiences they enjoy). |
| search_all_users_checkinsB | Search checkins across ALL registered users within an optional date range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a clearly distinct resource and action: user management (list/add/remove/get), checkin retrieval (per user and across all users), venue details, list details, and user-specific aggregates (venue history, mayorships, tastes). The only potential overlap is between get_user_checkins and get_user_venue_history, but the latter provides aggregated unique visit data, making the purposes distinct.
All tools use snake_case with a consistent verb_noun pattern (list_, add_, remove_, get_, search_). However, there is a minor inconsistency in pluralization: 'get_user_details' and 'get_venue_details' use plural 'details', while 'get_checkin_detail' and 'get_list_detail' use singular 'detail'.
With 13 tools, the server is well-scoped for its purpose, covering user management, checkin retrieval, venue details, lists, and user-specific data without being excessive or too thin.
The tool set covers core read operations for users, checkins, venues, and lists, plus user registration and deletion. However, a notable gap is the absence of venue search (e.g., searching venues by name or location), which is a common Foursquare API capability.