MCP getting started#

The Lindavia MCP package exposes the same published directory as the REST API through four read-only tools. Check that the remote domain resolves and passes an authenticated read before treating it as available:

Tool	Purpose
`search_businesses`	Search a bounded page by country, city, text, verification, and WhatsApp reachability.
`get_business`	Fetch one current published record by its Lindavia id.
`show_business`	Show that public business in an inline MCP App card.
`show_business_search`	Show a bounded search page in an inline MCP App card.

Remote server#

https://mcp.lindavia.com/mcp

Create a key in the developer console, then supply it as a Bearer token in the MCP connection:

{
  "mcpServers": {
    "lindavia": {
      "type": "http",
      "url": "https://mcp.lindavia.com/mcp",
      "headers": {
        "Authorization": "Bearer lnd_live_replace_me"
      }
    }
  }
}

Use your client's secret or environment-variable interpolation feature instead of committing the literal key to a configuration repository.

Local stdio transport#

The package can also run over stdio from this monorepo:

LINDAVIA_API_KEY='lnd_live_replace_me' \
  pnpm --dir lindavia/mcp exec node stdio.js

Tool behavior#

Tool results include concise Markdown for the model and bounded structured content for hosts. All tools call the versioned Lindavia REST API, so their authentication, field meanings, publication boundary, cursors, and rate-limit behavior match the Businesses API.

The two show_ tools reuse the existing read handlers. Compatible hosts can render their self-contained ui://lindavia/ resources inline. The resources are public static code; tool calls still require a developer key. A host must support a configured Bearer header. Lindavia does not currently offer MCP OAuth, and these resources do not establish ChatGPT or Claude directory publication.

Outreach requests

An agent may use whatsappEligible to identify records for review. The MCP server does not send messages, establish consent, or approve outreach. Apply the outreach data boundary before acting on a result.