ListingsAPI MCP

What listingsAPI MCP does

The listingsAPI MCP MCP server exposes Listings API account operations through MCP tools. Listings API stores business locations and synchronizes their information to more than 50 directories, maps, and search engines. Through an MCP-capable assistant, you can search and update locations, inspect listing coverage, review duplicate records, manage reviews and replies, publish posts, and read local performance data.

The underlying location record can include business details such as name, address, phone number, opening hours, categories, and photos. Connected account workflows also support linking Google or Facebook accounts, matching profiles to locations, and creating a new Google Business Profile listing when a location does not have one.

How it works

The listingsAPI MCP MCP server is hosted remotely at https://listingsapi.com/mcp and uses Streamable HTTP. No local package or build step is required. Configure an MCP client with the endpoint, then authenticate through the client’s OAuth browser flow or provide an API key in the required header.

OAuth 2.0 uses public clients, PKCE, dynamic client registration, and browser-based consent. Clients that need a static credential can send Authorization: API <your-key>. OAuth credentials apply to the MCP endpoint, while REST integrations use API keys.

Access levels matter. Read access is sufficient for lookups and reports. Write access is required for changing locations, replying to reviews, publishing posts, and connecting accounts.

Setup and configuration

Add the remote endpoint to a compatible client, or install the listing from a supported client directory. Claude Desktop can connect through the Listings API directory entry or through a custom connector URL. Cursor can use its directory listing or an MCP JSON configuration containing the endpoint. Claude Code supports an HTTP command with an optional authorization header.

Keep API keys in local client settings and out of shared repositories. OAuth-capable clients can complete sign-in without placing a key in configuration. A ListingsAPI account is required for production use.

Tools and capabilities

The listingsAPI MCP MCP server supports operations in these areas:

• Create, update, search, and inspect location profiles.
• List publishers covered by a plan and inspect listing states.
• Find duplicate listings for one location or an account, then mark or clear duplicate status.
• Read reviews, retrieve individual reviews by ID, inspect review analytics, and post supported replies.
• Read existing posts and publish posts to supported connected profiles.
• Retrieve Google, Facebook, and Bing metrics such as search views, map views, direction requests, calls, and website clicks for a requested date range.
• Link Google or Facebook accounts, match profiles, and create a Google Business Profile listing for an eligible location.

Limitations and notes

The listingsAPI MCP MCP server does not expose destructive operations such as archiving locations or deleting posts. Supported publishers and post payloads can vary, so check the current tool contract and server documentation before automating those workflows.

The optional Day Pass is availability-dependent, lasts 24 hours, supports up to two locations, and syncs only to 10 ListingsAPI demo directories. It does not write to real publishers and excludes reviews, posts, social features, analytics, connected accounts, and webhooks. A Day Pass key can be used locally with the same Authorization: API prefix.

Write operations affect connected account data and publisher profiles, so use a key with the appropriate access level and confirm publisher support before publishing.