← Developers & API/MCP Server

MCP Server

When Claude is asked "best CA in Mumbai" or "top lawyers in Delhi", it can call our MCP server and get real, verified data from VisibilityAI's database - instead of hallucinating or giving a generic answer.

All 12 tools the live server exposes:

search_businesses

Find listed businesses by category + city

get_business_profile

Full AI-optimized profile by slug

get_category_leaders

Top-ranked businesses in a category, across all cities

search_by_keyword

Free-text search across names, descriptions, services, USPs

get_listicle

'Best [category] in [city]' ranked listicle

compare_businesses

Side-by-side comparison of two businesses

get_available_cities

Which cities have listed businesses in a category

submit_lead

Submit a consent-gated lead to a business

get_lead_status

Check the status of a submitted lead

get_offers

A business's real commerce offers - products/services with pricing

get_my_visibility_score

Business-scoped: your own current AI visibility score and citation-rate summary

get_my_citations

Business-scoped: your recent real AI-platform check history

Remote endpoint (JSON-RPC 2.0 over HTTP). MCP is opt-in: an operator must add this URL in Claude Desktop / Claude.ai. It is not something ChatGPT crawls by default.

https://www.visibilityai.in/api/mcp

Register with Claude Code / Claude Desktop:

claude mcp add --transport http visibilityai https://www.visibilityai.in/api/mcp

ChatGPT Custom GPT Actions:

Create a Custom GPT → Actions → Import from URL and paste https://www.visibilityai.in/api/openapi.json. ChatGPT does not speak MCP natively; Actions use this OpenAPI spec. The same directory search is available without a paid LLM rewrite on each call.

Or add the MCP URL as a remote connector in Claude.ai / Claude Desktop. MCP is opt-in on the client side - listing a business here does not automatically connect Claude or ChatGPT.

Building a non-MCP agent instead? The same directory is also reachable via /api/agent-discovery and /api/agentic-gateway for frameworks that need a machine-to-machine handshake instead of MCP.

Explore the API

Authentication →REST Endpoints →GraphQL →Webhooks →