Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
UniFi controller: clients, devices, WLANs, health, alarms, events, sysinfo, identity.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"lancontrol": {
"command": "npx",
"args": [
"-y",
"@reneturcios/lancontrol",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add lancontrol -- npx -y @reneturcios/lancontrol mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lancontrol": {
"command": "npx",
"args": [
"-y",
"@reneturcios/lancontrol",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lancontrol": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/lancontrol",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
lancontrol reads UniFi Network controller state through a single action-router tool: connected clients, network devices, WLAN configurations, site health, active alarms, recent events, controller sysinfo, and the authenticated identity. One binary serves a command-line interface and a stdio MCP server.
This is a labelled core subset. The upstream surface defines 267 actions in total; lancontrol builds only the 8 preserved convenience actions plus help (9 action values). The generated families are omitted, on purpose and by name: official_* (78 actions), unifi_* (175 actions), and the 5 hybrid aliases (list_clients, list_devices, list_networks, list_wifi, get_system_info).
Both variables are required for every action except help; a missing value errors before any request is made:
| Variable | Required | Purpose |
|---|---|---|
UNIFI_URL | yes | Controller base URL, e.g. https://unifi.local. |
UNIFI_API_KEY | yes | API key, sent as the X-API-KEY header. |
UNIFI_SITE | no | UniFi site name. Defaults to default. |
Never pass the API key as a tool argument; it is read from the environment only.
npx @reneturcios/lancontrol help
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/lancontrol
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
lancontrol clients
lancontrol devices lancontrol wlans lancontrol health lancontrol alarms lancontrol events --limit 25 lancontrol sysinfo lancontrol me lancontrol help
lancontrol --version
Action commands print the upstream JSON payload. help prints the local action documentation and needs no configuration and no network. Exit codes: 0 on success, 1 when a call fails (including a missing-config or upstream API error), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/lancontrol mcp
MCP client configuration:
{
"mcpServers": { "lancontrol": { "command": "npx", "args": ["-y", "@reneturcios/lancontrol", "mcp"], "env": { "UNIFI_URL": "https://unifi.local", "UNIFI_API_KEY": "...", "UNIFI_SITE": "default" } } } }
One tool is exposed:
| Tool | Input | What it returns |
|---|---|---|
unifi | action (required, one of the 9 subset values), limit (optional integer, events only) | The upstream payload for the chosen action, or local documentation for help. |
| Action | Description |
|---|---|
clients | Connected wireless and wired clients. |
devices | Network devices: APs, switches, gateways. |
wlans | WiFi network configurations. |
health | Site health summary. |
alarms | Active alarms and alerts. |
events | Recent controller events. |
sysinfo | Controller system information. |
me | Authenticated UniFi identity. |
help | Built-in action documentation. |
The public spec names the actions but does not publish, in its convenience-action table, the exact controller path for each one. Each action is therefore implemented as a GET to a plausible documented UniFi internal endpoint under UNIFI_URL, with the X-API-KEY header:
| Action | Endpoint |
|---|---|
clients | GET /proxy/network/api/s/{site}/stat/sta |
devices | GET /proxy/network/api/s/{site}/stat/device |
wlans | GET /proxy/network/api/s/{site}/rest/wlanconf |
health | GET /proxy/network/api/s/{site}/stat/health |
alarms | GET /proxy/network/api/s/{site}/stat/alarm |
events | GET /proxy/network/api/s/{site}/stat/event (plus ?_limit={limit} when a limit is supplied) |
sysinfo | GET /proxy/network/api/s/{site}/stat/sysinfo |
me | GET /proxy/network/api/self |
help | no request — answered locally |
HTTP failures surface the status plus the upstream message (meta.msg, message, or error) when present.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx
MIT — see LICENSE.