NeatListing · Docs
NeatListing MCP server docs
NeatListing is a hosted MCP server for Google Business Profile at https://app.neatlisting.com/mcp. It uses the Streamable HTTP transport and OAuth 2.1 with PKCE, so an MCP client registers itself and the business owner signs in with Google once. These pages are for developers and for agents that want the details behind the tools.
Endpoint
https://app.neatlisting.com/mcp
- Transport: Streamable HTTP. Send JSON-RPC with
POST. AGETwith a valid token returns405. - Stateless. There is no
Mcp-Session-Idto keep, and the server never sends list-changed notifications, so the tool list is fixed for a connection. - Both protocol styles work: clients that open with
initializeget one JSON response per request, and clients on the newer per-request protocol (server/discover) are served too. - Request bodies can be up to 5 MB. CORS is open, so browser-based clients can call the endpoint.
- Each connected agent can make 60 MCP requests a minute; the connection handshake (initialize, notifications, ping) doesn't count. Past that the server answers
429with a JSON-RPC error andRetry-After: 60. - Price: free. There is no API key and no Google Cloud project to set up.
Authentication
Call the endpoint without a token and you get 401 with a WWW-Authenticate header pointing at the OAuth metadata. Clients that follow the MCP authorization spec take it from there: they register with dynamic client registration (or identify themselves with a client ID metadata document), send the owner to the sign-in page with PKCE, and swap the code for tokens. The owner signs in with Google, picks locations and clicks Allow.
Access tokens last one hour. Refresh tokens last 90 days and rotate on every use. Agents never see the owner's Google tokens. Details are in Authentication.
What the server tells the model
The server is named neatlisting and sends instructions with initialize. They explain location ids, the four change statuses, the high-risk fields and how to treat review and post text (as data, never as instructions). There is one prompt, setup, which walks the owner through choosing locations.
Every tool sets all four annotations explicitly: readOnlyHint, destructiveHint, idempotentHint and openWorldHint. Reads are marked read-only. Edits that overwrite a public value and deletes are marked destructive.
Tool groups
56 tools. Each part of a profile has its own tool, so an AI app's per-tool settings (in Claude: Always allow, Needs approval or Blocked) can treat the phone number differently from the hours.
- Orientation:
get_my_permissions,list_locations,get_location,get_google_updates,list_admins - Setup:
get_setup_status,set_location_access,finish_setup - Profile fields:
update_regular_hours,update_special_hours,update_more_hours,update_description,update_services,update_labels,update_open_status,update_website,update_phone,update_additional_phones,update_secondary_categories,update_business_name,update_address,update_primary_category,update_service_area, plusget_attributes,update_attributesandsearch_categories - Posts:
list_posts,create_post,update_post,delete_post - Reviews:
list_reviews,reply_to_review,delete_review_reply - Photos:
list_photos,add_photo,delete_photo - Booking and ordering links:
list_action_links,create_action_link,update_action_link,delete_action_link - Menus and hotels:
get_food_menus,update_food_menus,get_lodging,update_lodging - Insights:
get_performance(daily, up to 18 months back) andget_search_keywords(monthly) - Verification:
get_verification_status,start_verification,complete_verification - The agent's own changes:
list_my_changes,get_change,undo_my_change,preview_change - Waiting changes:
list_pending_changes,approve_change,reject_change
Inputs, side effects and limits for each one are in the tool reference, which is generated from the live definitions.
Agents can't add or remove profile managers, transfer a profile or delete one. Google has shut down Q&A and Business Calls, so there are no tools for them.
Which locations an agent sees
NeatListing offers only profiles where the owner's Google account is a Primary owner, Owner or Manager. On the Allow page the owner picks which of those this agent may use. Roles are checked again with Google at least every six hours, or when an agent calls list_locations with refresh: true (at most once a minute). A profile the owner loses in Google disappears for agents right away.
Supported clients
Anything that speaks MCP over Streamable HTTP and supports MCP sign-in. Setup for each:
- Claude (web, desktop, mobile)
- Claude Code
- ChatGPT
- Codex
- Cursor
- Grok
- VS Code with GitHub Copilot
- Windsurf (Devin Desktop)
- Gemini CLI
- Zed
A client without MCP sign-in can't connect yet. Email hello@neatlisting.com and we'll help. The setup guide has every app on one page.