> ## Documentation Index
> Fetch the complete documentation index at: https://www.landbase.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Landbase MCP

> Connect Codex, Claude Code, Cursor, or VS Code to Landbase MCP.

Use `https://mcp.landbase.com/mcp` with Streamable HTTP and OAuth. Choose your
client below, complete Landbase sign-in, and then check the connection.

## Codex

Add Landbase from a terminal:

```bash theme={null}
codex mcp add landbase --url https://mcp.landbase.com/mcp
```

Complete the sign-in prompt if one opens. If authorization is still needed, run:

```bash theme={null}
codex mcp login landbase
```

Check that the entry exists with `codex mcp list`. Then start a Codex chat and
ask it to call `list_accounts` through the Landbase server.

See the [official Codex MCP documentation](https://developers.openai.com/codex/mcp)
for configuration details.

## Claude Code

Add the remote server from a terminal:

```bash theme={null}
claude mcp add --transport http landbase https://mcp.landbase.com/mcp
```

Start Claude Code, run `/mcp`, select Landbase, and complete its authentication
flow. Ask Claude to call `list_accounts` after connecting.

See the [official Claude Code MCP documentation](https://code.claude.com/docs/en/mcp)
for configuration scope and authentication options.

## Cursor

Add this entry to `.cursor/mcp.json` in your project, merging it with any
existing `mcpServers` entries:

```json theme={null}
{
  "mcpServers": {
    "landbase": {
      "url": "https://mcp.landbase.com/mcp"
    }
  }
}
```

In Cursor's MCP settings, connect Landbase and complete OAuth sign-in when
prompted. In an agent chat, enable the Landbase tools and ask it to call
`list_accounts`.

See the [official Cursor MCP documentation](https://cursor.com/docs/mcp) for
user-level configuration and the current settings interface.

## VS Code

Run **MCP: Add Server** from the Command Palette, choose **HTTP**, and enter
`https://mcp.landbase.com/mcp`. Name the server `landbase` and choose where to
save the configuration.

For workspace configuration, the entry in `.vscode/mcp.json` is:

```json theme={null}
{
  "servers": {
    "landbase": {
      "type": "http",
      "url": "https://mcp.landbase.com/mcp"
    }
  }
}
```

Start the server through VS Code's MCP controls, review the trust prompt, and
complete OAuth sign-in when prompted. Open an agent chat, enable the Landbase
tools, and ask it to call `list_accounts`.

See the [official VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
for prerequisites and server controls.

## Check the connection

A successful `list_accounts` call returns your user and Landbase accounts. If
more than one account is returned, choose one and have the assistant use its
string `account_id` on every account-scoped call, including polling, retries,
confirmation calls, and downloads. The server does not retain account selection
between calls. Seeing a server in the client's
configuration list alone does not establish that sign-in succeeded.

Next, [build your first prospect list](https://www.landbase.com/docs/guides/mcp/first-prospect-list.md).

## Sign-in and account selection

Use your client's OAuth sign-in action to connect your Landbase account.
If you need to sign in again, reconnect through the same client. Do not paste
access tokens or authorization codes into chat or support messages.

After sign-in, use `list_accounts` to choose the Landbase account for your
work. Passing an `account_id` selects an account for a tool call; it does not
grant access to that account.

## Troubleshooting

* **No sign-in action:** check that the client supports remote Streamable HTTP
  servers and OAuth. A client that supports only stdio cannot use this URL directly.
* **Authorization rejected:** verify `https://mcp.landbase.com/mcp`, then
  reconnect through the client's sign-in flow.
* **Several accounts:** call `list_accounts`, choose an account, and pass
  `account_id`. Do not guess an account ID.
* **A search is still running:** keep its handle and call `get_search_result`.
  See [Continue a search or workflow](https://www.landbase.com/docs/guides/mcp/continue-async-work.md).
* **Temporary token-verification outage:** a `503` can mean the server could
  not check your sign-in. Retry after the indicated delay rather than
  immediately discarding your sign-in.
* For more recovery cases, see [Troubleshoot MCP](https://www.landbase.com/docs/guides/mcp/troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.