
Nexus UI MCP server
Which MCP servers are Nexus UI's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-10
- Addresshttps://nexus-ui.dev/mcpnot in the official registry: answered when asked
No entry in the official MCP registry names this server. It answered on nexus-ui.dev when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.
- Stateanswerschecked 2026-10-27
- Tools2
- Server calls itselfnexus-ui-docs-mcp
- Server version1.0.0
- Protocol version2024-11-05
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 137 ms.
- Its tools do none of the product's use cases we checked: Add a prompt input with a model picker; Let users toggle extended thinking per request; Display chain of thought and reasoning steps.
Once connected
- Parameters are untyped or undescribed in 1 of 2 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score65 of 100answers 94 · does the job 0 · definitions 75 · context 100 · connects 100
- What an agent can do with it0 of 3 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer1555 ms
- Space in an agent's context≈ 129 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsB · 75 of 100
- Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 2
- Not saying whether it only reads or can destroy: 2 of 2
What an agent can do with it
- cannot · Add a prompt input with a model picker
- cannot · Let users toggle extended thinking per request
- cannot · Display chain of thought and reasoning steps
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_docsSearch Nexus UI docs pages by title and description
get_docGet markdown content for a docs page URL or path
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"nexus-ui": {
"type": "http",
"url": "https://nexus-ui.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http nexus-ui https://nexus-ui.dev/mcpclaude.ai, ChatGPT and other clients: add https://nexus-ui.dev/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.