Cursor and other clients
Who this is for: users of Cursor, Codex CLI or any other MCP-capable tool.
-
In your client, add a remote MCP server (sometimes called “custom connector” or “HTTP server”) named Bakulai with this URL:
https://erp.bakulai.com/mcp -
The first call opens the Bakulai sign-in and the consent screen in your browser; press Allow.
-
The Bakulai tools appear in the client’s tool list.
Verified and not
Section titled “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
Section titled “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
Section titled “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 desktop app.
