Connect Cursor

Add the docs server beside the MCP servers you already have. Setup time is about 10 minutes once an endpoint is actually running.

Purpose

Cursor lists search_docs and list_doc_sections. Evidence level: the JSON shape was checked against Cursor’s published MCP guide (mcpServers with a url). The Cursor application itself was not smoke-tested in this change.

Prerequisites

Cursor with remote MCP support. A docs endpoint your admin has started. Do not point production users at https://docs.bundata.com/api/mcp until that route is deployed.

Sample

Query inside Cursor after connect: search_docs with upload-url. Expect the upload recipe’s title and a Markdown URL.

Steps

1. Open Cursor Settings, MCP, and edit the config. Preserve every server already listed.
2. Add a bundata-docs entry under mcpServers with url set to the host you were given. For a local process that is http://127.0.0.1 plus the port and /api/mcp.
3. Reload MCP servers. Confirm the two tool names. There is no authentication header for public docs.
4. Run one English query and one Japanese query. Disconnect by deleting only the bundata-docs key.

Fields

Example

{"mcpServers":{"bundata-docs":{"url":"http://127.0.0.1:8787/api/mcp"}}}

Replace the url when you are given a deployed host. Do not commit a password into this file.

Recovery

If the server is absent, Cursor shows a connection error. That is expected while the route is not deployed. Fix the url. Do not install a third-party bridge to hide the error.

Limits

This page is source-checked, not a recorded Cursor UI session. Tools remain read-only.

Check

Success: both tool names appear and a query returns a snippet plus a Markdown URL. Failure: a missing server stays an error, and no other mcpServers entry was removed.