Before you start
You need:- A Landbase account with access to the account you want to use.
- A Grok Bot account with custom MCP servers enabled.
- A browser available to complete Landbase OAuth.
Add Landbase to Grok Bot
In a Grok Bot chat, paste:@.
Verify the connection
Ask Grok Bot:account_id on every later account-scoped call.
Seeing Landbase in the plugin list does not prove that OAuth succeeded. The list_accounts call is the connection check.
Run a safe first search
Ask:Before paid work
Ask Grok Bot 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 returnedaccount_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
Grok Bot cannot add the server
Confirm that the URL is exactlyhttps://mcp.landbase.com/mcp and that custom MCP access is enabled for the Grok account. Business and Enterprise users may need an administrator to provision the connector first.
OAuth completed but no tools appear
Start a new chat and attach Landbase with@. If the client reports the connection as disconnected, remove and reconnect Landbase through the client’s connector settings.
Grok uses the wrong account
Calllist_accounts, ask which account to use, and pass the chosen 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. Useget_search_result for a search handle and get_workflow_run for a workflow run ID. See Continue a search or workflow.

