Service · AI tools
Connect the Windrose Knowledge Database to your AI tools
The Windrose Knowledge Database is a remote MCP (Model Context Protocol) server. Connect it to Grok, Claude, ChatGPT or Cursor and ask about Windrose products directly. Every result comes with the file name and a Google Drive link.
Public read-only access, no Windrose account needed
For customers, partners and service providers without a @windrose.ai account, for example people who use Grok, Claude, ChatGPT or Cursor.
- Server URL
https://15-224-47-159.sslip.io/mcp/public- Transport
- Streamable HTTP
- Sign-in
- None: no login, no header, no token
- Tools
searchfinds product documents and returns the file name, date, type, part numbers, a public summary and the Drive link.askgives a short answer with sources. No company memory, no part fact cards, no write access.- Included
- Product details only: product and component specifications, technical data sheets and datasheets; functional specifications, CAN/LIN communication matrices and DBC files, interface definitions; drawings and CAD models (2D drawings, 3D and assembly models, circuit diagrams, schematics); product, user and service manuals, including the service-manual DITA chapters; diagnostic specifications and fault-code tables; parts catalogues; product introductions, catalogues and configuration sheets.
- Not included
- Reports of any kind (including test, inspection and validation reports), meeting notes and weekly reports, plans, software code and calibration data, reviews and change records, BOMs, certification and regulatory files, contracts, invoices, finance, HR, fundraising and due-diligence files, confidential and commercial files, restricted folders, and the Windrose Software and General Management shared drives.
- Rate limits
- Per IP address: 20 tool calls per minute and 400 per day, of which 40
askcalls per day. All public users together: 8,000 calls per day, of which 800askcalls. - Drive links
- The links point to Windrose's internal Google Drive and usually cannot be opened from outside Windrose. Use the file name and summary, and ask Windrose for the document if you need it.
Set it up in your AI tool
Grok: in Connectors, add a custom MCP server with the URL https://15-224-47-159.sslip.io/mcp/public, authentication None and no headers. Then try: “Search the Windrose knowledge database for WH11 fault code B111716”.
ChatGPT (Developer mode): Create connector, MCP Server URL https://15-224-47-159.sslip.io/mcp/public, Authentication No authentication.
Claude: Settings → Connectors → Add custom connector, URL https://15-224-47-159.sslip.io/mcp/public. Leave the OAuth fields empty.
Cursor: add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"windrose-kb-public": { "url": "https://15-224-47-159.sslip.io/mcp/public" }
}
}
Quick check from a terminal:
curl -s https://15-224-47-159.sslip.io/mcp/public \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Windrose colleagues: keep using the token-protected /mcp endpoint below. It returns fuller results and adds company memory and part fact cards.
Tools
| Tool | What it does | Parameters |
|---|---|---|
search | Searches file names, file contents and meaning, in Chinese, English or a mix. It also finds 7-digit part numbers and model codes such as WH11 or X9D01. | query (required); limit (optional, 1–50, default 10) |
ask | Ask in plain language. The database checks the files and company memory, writes an answer with numbered citations [n] and lists the source files (file name and Drive link). Slower than search: up to about 1 minute. | question (required) |
memory_read | Windrose colleagues only. Reads company memory: decisions and corrections recorded by colleagues, which take priority over older files. | query (optional; without it you get the latest 200 entries) |
Nothing can be written over MCP: no memory writes, and no Google Drive file is changed, moved or deleted.
For Windrose colleagues (@windrose.ai account)
Endpoint https://15-224-47-159.sslip.io/mcp, transport Streamable HTTP, read-only. It uses the same sign-in and permissions as the web version of the Knowledge Database. Only @windrose.ai colleagues can use it.
Results follow your own permissions
- The web version, the REST API and MCP apply the same rules, so the same question can give different colleagues different results.
- Every colleague sees the general technical and business documents in the Windrose Technology Database and Windrose Global shared drives.
- Only authorised people see most contract and finance files, HR files, fundraising, due-diligence and corporate-governance files, folders marked confidential, commercial and business-plan folders, and the Windrose Software and General Management shared drives. A file in any restricted category stays restricted.
- If you cannot find a file, it may exist but sit outside your permissions. Ask Wen if your work needs access. Do not forward documents to people who do not have access.
Each search result has file_name, drive_link, doc_type, doc_date, suppliers, part_numbers, summary, key_facts and snippet.
Step 1: get your personal Agent token
- Open the Knowledge Database web app with your @windrose.ai Google account: Knowledge Database web app
- Open the Agent token tab and generate a token.
- Copy the token. It starts with
wtd_.
Your token works like your password: queries are logged under your name. Do not post it in chats, commit it to Git or share screenshots of it. If it leaks, ask Wen to revoke it and generate a new one.
In every example below, replace wtd_YOUR_TOKEN with your own token.
Claude Desktop
Claude Desktop connects through the small mcp-remote tool. It needs Node.js 18 or later (nodejs.org) for the npx command.
Open Settings → Developer → Edit Config. This opens claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json). Add the windrose-kb entry; if the file already has mcpServers, add only that entry.
{
"mcpServers": {
"windrose-kb": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://15-224-47-159.sslip.io/mcp",
"--header",
"Authorization:${KB_AUTH}"
],
"env": {
"KB_AUTH": "Bearer wtd_YOUR_TOKEN"
}
}
}
}
Put one space between Bearer and the token, and no space after the colon in Authorization:${KB_AUTH}. That is the form mcp-remote recommends; it avoids a space problem on Windows.
Save, quit Claude Desktop completely and reopen it. Under the tools icon you should see windrose-kb with three tools. Try: “Search the Windrose knowledge database for the WH12 low-voltage harness drawing and give me the file link”.
Claude's Custom Connector (Settings → Connectors) needs Google sign-in (OAuth), which the server has not enabled yet, so use the config file for now.
Cursor
Cursor supports remote MCP with custom headers, so no Node.js is needed. Open or create ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json), or go to Cursor Settings → MCP → Add Custom MCP, and add:
{
"mcpServers": {
"windrose-kb": {
"url": "https://15-224-47-159.sslip.io/mcp",
"headers": {
"Authorization": "Bearer wtd_YOUR_TOKEN"
}
}
}
}
Safer option: keep the token in the environment variable WINDROSE_KB_TOKEN and write "Authorization": "Bearer ${env:WINDROSE_KB_TOKEN}".
Back in Cursor's MCP settings, windrose-kb should show a green dot and 3 tools. If not, toggle it or refresh. Then ask in the Agent chat, for example: “Use windrose-kb to search for the EU electrical schematic”.
ChatGPT
As of October 2026, ChatGPT connectors (including Developer mode) support only OAuth browser sign-in or no authentication. They cannot send custom headers, so personal tokens do not work. The colleague endpoint does not allow anonymous access and OAuth is not enabled yet, so ChatGPT cannot connect to it for now. For public documents, use the public endpoint above with No authentication.
Once OAuth is enabled (we will announce it): Settings → Apps & Connectors → Advanced settings → turn on Developer mode. Create a connector named Windrose Knowledge Database with MCP Server URL https://15-224-47-159.sslip.io/mcp and Authentication OAuth, then sign in with your @windrose.ai account.
Other tools
Claude Code (command line):
claude mcp add --transport http windrose-kb https://15-224-47-159.sslip.io/mcp --header "Authorization: Bearer wtd_YOUR_TOKEN"
Any other MCP client that supports Streamable HTTP and custom headers: URL https://15-224-47-159.sslip.io/mcp, header Authorization: Bearer wtd_YOUR_TOKEN.
Check the connection
Replace wtd_YOUR_TOKEN with your token and run this in a terminal:
curl -s https://15-224-47-159.sslip.io/mcp \
-H "Authorization: Bearer wtd_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
If you see search, ask and memory_read, the token works.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| 401 / “unauthorized” | No token, an incomplete token, or the Bearer prefix is missing. Copy the token again and check the format Bearer wtd_.... |
| No tools in Claude Desktop | Check that Node.js is installed and the JSON is valid (commas, quotes), then quit Claude Desktop completely and reopen it. Error logs are under Settings → Developer. |
| Red dot in Cursor | Check that the URL in mcp.json ends in /mcp and that headers is written correctly. |
ask is slow | Normal: it searches and writes a full answer, which takes up to about 1 minute. Use search when you only need files. |
| Drive link does not open (no @windrose.ai account) | Normal: the Drive is internal to Windrose. Use the file name and summary, or ask Windrose for the file. |
| Drive link does not open (Windrose colleague) | The link uses your own Google permissions. If you have no access to that file on Drive, request it from the file owner. |
Questions? Contact Windrose.