Cursor writes the median interface.
An editor gives the agent your code but not your taste. Ask for a settings screen and you get the same card grid every other Cursor project ships. One JSON block gives it somewhere to look.
The code is in front of it. The design is not.
Cursor is excellent at what it can see: your components, your styles, your conventions. The moment a screen does not exist yet, it falls back on the most common pattern in its training data — the three-card feature row, the rounded pill button, the empty state with a single centred illustration.
A reference library changes the input, not the model. Your agent calls a tool, gets back named screens and flows from products that shipped them, and designs from what it just read. The mechanism is the same UI-reference MCP server that works in any client.
One object, two possible files.
Your key comes from your account page. There is nothing to install locally: the server is hosted and speaks streamable HTTP.
{
"mcpServers": {
"thinkui": {
"url": "https://thinkui.xyz/mcp",
"headers": { "Authorization": "Bearer your-key" }
}
}
}
Add to Cursor opens Cursor with the server pre-filled — replace YOUR_KEY with the key from your account page.
Check it
Cursor Settings → MCP. The entry must be green. Red means the JSON did not parse or the URL is wrong, and Cursor will not tell you which beyond the error line.
Use it
Agent mode, not Ask. Tools are called by the agent loop; in Ask mode the model may describe the call without making it.
Share it
Commit the project file with the header written as an environment variable, and say in the README which one to set. A committed key is a leaked key.
Ask in terms of a decision.
Better
"Look up how dashboards frame an empty first-run state before you build the home screen."
"Find a pricing table that does not look like a SaaS template, then build the billing page."
Worse
"Make it beautiful."
"Use a modern design."
Neither names a decision, so there is nothing for the library to match and nothing for the agent to cite.
Questions this page gets.
Where do I put the MCP config in Cursor?
Project scope is .cursor/mcp.json at the repository root; user scope is ~/.cursor/mcp.json so every project gets it. The same object goes in either file, under an mcpServers key.
Why is the server not showing up?
Cursor reads MCP configuration at start-up, so a server added while the app is open does not appear until you restart it. A red dot in Cursor Settings → MCP means the JSON did not parse or the URL is wrong.
Do the tools work in Ask mode?
Tools belong to agent behaviour. Use Agent mode; in Ask mode the model may describe what it would call without calling anything.
Can I commit the config to a shared repo?
Yes, if the key is not in it. Write the header value as a variable Cursor expands from the environment and document the variable in the project README.
Something to look at, in one block.
Create an account, paste the object, restart Cursor, and ask for a screen you have opinions about.