Skip to main content

​
Configure Cursor and Grok Bot for Landbase MCP

Cursor and Grok Bot are related client surfaces, but their Landbase MCP setup looks different. Use the section for the client you are configuring. First review the common Connect Landbase MCP flow.

​
Before you start

You need:
  • A Landbase account with access to the account you want to use.
  • A browser available to complete Landbase OAuth.
  • Cursor with MCP support, or Grok Bot with custom MCP servers enabled.

​
Configure Cursor

Add this entry to .cursor/mcp.json, merging it with existing servers:
Connect Landbase from Cursor’s MCP settings and complete OAuth. Ask the agent to call list_accounts before starting a search.

​
Configure Grok Bot

In a Grok Bot chat, paste:
Review the server name and URL before approving. When Grok opens the Landbase authorization page, sign in and approve access. Then start a new chat and attach Landbase with @.

​
Verify the connection

Ask the client:
If more than one account is returned, choose the intended account before searching. Pass the selected account_id on every later account-scoped call. Seeing Landbase in a plugin or connector list does not prove that OAuth succeeded; list_accounts is the connection check. Ask either client:
The assistant should show the dataset, row count, available fields, and a preview before any paid follow-up work.

​
Before paid work

Ask the client to show the credit quote or row count and wait for approval before running enrichment, qualification, research, contact enrichment, publishing, or a paid download. Keep the returned account_id, dataset ID, search handle, and workflow run ID. If an operation is still running, continue polling the existing handle or run ID instead of starting the same request again.

​
Troubleshooting

​
The client cannot add the server

Confirm that the URL is exactly https://mcp.landbase.com/mcp. Cursor users should check .cursor/mcp.json; Grok Bot users should confirm that custom MCP access is enabled. Business and Enterprise users may need an administrator to provision the connector.

​
OAuth completed but no tools appear

For Cursor, reconnect Landbase through the MCP settings. For Grok Bot, start a new chat and attach Landbase with @. If the client reports the connection as disconnected, remove and reconnect the server.

​
The client uses the wrong account

Call list_accounts, choose the intended account, and pass its account_id on every account-scoped call. Never infer an account from a dataset ID or run ID.

​
A search or workflow is still running

Keep the returned identifier and continue the existing operation. Use get_search_result for a search handle and get_workflow_run for a workflow run ID. See Continue a search or workflow.

​
Disconnecting Landbase

Remove Landbase from Cursor’s MCP settings or Grok Bot’s plugins/connectors. You can also revoke the connected client from Landbase settings.

​
Next steps