---
app: integrations
audience:
  - owner
ui_only: true
agent_actions: []
agent_examples:
  - connect Cursor to Bakulai
  - does Windsurf work with Bakulai?
llm_weight: normal
title: Cursor and other clients
description: Any client that speaks Streamable HTTP with OAuth sign-in can add
  Bakulai as a remote MCP server; Cursor is verified.
editUrl: true
head: []
template: doc
sidebar:
  order: 5
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

import { Steps } from "@astrojs/starlight/components";

**Who this is for:** users of Cursor, Codex CLI or any other MCP-capable tool.

## Steps

<Steps>

1. In your client, add a **remote MCP server** (sometimes called "custom connector" or "HTTP server") named **Bakulai** with this URL:

   ```text
   https://erp.bakulai.com/mcp
   ```

2. The first call opens the Bakulai sign-in and the consent screen in your browser; press **Allow**.

3. The Bakulai tools appear in the client's tool list.

</Steps>

## Verified and not

- **Cursor** — verified. Cursor Settings → MCP → add a server with the URL above; the first call opens the sign-in.
- **Codex CLI** — registers the same kind of sign-in redirect and should work; not verified yet.
- **Windsurf** — not supported: it registers a custom-scheme redirect our sign-in does not accept.

## Limits & safety

The client must support **Streamable HTTP** transport and **OAuth 2.1** sign-in with dynamic client registration — that is what "remote MCP server" means in most clients today. Clients that only speak stdio need a bridge; Bakulai does not ship one.

## Troubleshooting

- **The client asks for a token or API key.** There is none: the sign-in is your Bakulai login. Leave the field empty and let the client open the browser.
- **Sign-in rejected with an error about the redirect URL.** The client uses an address our sign-in does not accept (see Windsurf above). Use another client, or the [Bakulai Agent](/agent/) desktop app.

[Disconnect an agent](/integrations/disconnect/) · [Integrations](/integrations/)