ucontrol-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ucontrol-mcplist all schema definitions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ucontrol-mcp
MCP stdio server for the uControl Schema, uAsset, and uMap APIs documented in:
DOCC80-API Settings-060526-173133.pdfDOCC80-Schema API's-060526-173649.pdfDOCC80-uAsset API's-060526-173407.pdfDOCC80-uMap API's-060526-173553.pdf
The server deliberately separates protocols by access type:
Read-only tools are named
ucontrol_read_*and are registered withreadOnlyHint: true.Write/mutation tools are named
ucontrol_write_*and are registered withreadOnlyHint: false.Destructive write tools, such as delete, remove, unlink, and decommission operations, are registered with
destructiveHint: true.ucontrol_read_protocolsreturns the complete local inventory with read/write/destructive classification and whether each tool is currently registered.
Install
npm install
npm run buildRelated MCP server: mcpdeployment
Configuration
Required:
UCONTROL_BASE_URL=https://ucontrol.example.com/uControlOptional:
UCONTROL_API_TOKEN=...
UCONTROL_COOKIE=JSESSIONID=...
UCONTROL_TIMEOUT_MS=30000
UCONTROL_TOOL_MODE=read-only
UCONTROL_ALLOW_WRITES=falseAuthentication follows the API Settings document: uControl can be configured to require bearer-token authentication, and authenticated users must be in the API-Access team.
UCONTROL_BASE_URL should normally include the /uControl context path. The server appends documented API paths such as /api/schema/definitions.
Read-only mode
This is the default. Only ucontrol_read_* tools are registered.
{
"mcpServers": {
"ucontrol": {
"command": "node",
"args": ["/Volumes/Hub/Code/GitHub/ucontrol-mcp/dist/index.js"],
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "replace-me",
"UCONTROL_TOOL_MODE": "read-only"
}
}
}
}Read/write mode
Write tools are registered only when UCONTROL_TOOL_MODE=read-write. They still refuse to execute unless UCONTROL_ALLOW_WRITES=true.
{
"mcpServers": {
"ucontrol": {
"command": "node",
"args": ["/Volumes/Hub/Code/GitHub/ucontrol-mcp/dist/index.js"],
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "replace-me",
"UCONTROL_TOOL_MODE": "read-write",
"UCONTROL_ALLOW_WRITES": "true"
}
}
}
}LM Studio setup
LM Studio can run local stdio MCP servers from its MCP configuration. Build this project first, then add the server in LM Studio's MCP settings. If LM Studio exposes an Edit mcp.json action, use that; otherwise add the same JSON through its MCP server UI.
From this repository:
cd /Volumes/Hub/Code/GitHub/ucontrol-mcp
npm install
npm run buildRecommended starting configuration is read-only:
{
"mcpServers": {
"ucontrol": {
"command": "node",
"args": ["/Volumes/Hub/Code/GitHub/ucontrol-mcp/dist/index.js"],
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "replace-me",
"UCONTROL_TOOL_MODE": "read-only"
}
}
}
}If LM Studio cannot find node, replace "command": "node" with the absolute path from:
which nodeFor write access, change the environment block explicitly:
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "replace-me",
"UCONTROL_TOOL_MODE": "read-write",
"UCONTROL_ALLOW_WRITES": "true"
}Restart or reload LM Studio's MCP servers after saving the configuration. In a chat, verify the connection with:
Use the ucontrol_read_protocols tool and summarize which uControl tools are registered.Expected behavior:
In read-only mode, only
ucontrol_read_*tools appear as registered.In read/write mode,
ucontrol_write_*tools also appear, but write calls still fail unlessUCONTROL_ALLOW_WRITES=true.If uControl requires authentication, the API token must belong to a user in the API-Access team.
VS Code setup
VS Code supports MCP servers through an mcp.json file. You can configure this server either for one workspace or for your VS Code user profile.
Options:
Workspace config: create or edit
.vscode/mcp.jsonin the workspace where you want the server available.User config: run MCP: Open User Configuration from the Command Palette.
Guided flow: run MCP: Add Server from the Command Palette and choose Workspace or Global.
Build the server first:
cd /Volumes/Hub/Code/GitHub/ucontrol-mcp
npm install
npm run buildRecommended read-only .vscode/mcp.json:
{
"inputs": [
{
"type": "promptString",
"id": "ucontrol-api-token",
"description": "uControl API bearer token",
"password": true
}
],
"servers": {
"ucontrol": {
"type": "stdio",
"command": "node",
"args": ["/Volumes/Hub/Code/GitHub/ucontrol-mcp/dist/index.js"],
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "${input:ucontrol-api-token}",
"UCONTROL_TOOL_MODE": "read-only"
}
}
}
}For write access, change only the environment values intentionally:
"env": {
"UCONTROL_BASE_URL": "https://ucontrol.example.com/uControl",
"UCONTROL_API_TOKEN": "${input:ucontrol-api-token}",
"UCONTROL_TOOL_MODE": "read-write",
"UCONTROL_ALLOW_WRITES": "true"
}After saving the config, start or restart the server with MCP: List Servers, then select ucontrol and choose Start or Restart. VS Code may ask you to trust the local server before exposing its tools in chat.
Verification prompt in VS Code Chat:
Use the ucontrol_read_protocols tool and summarize which uControl tools are registered.Troubleshooting:
If VS Code cannot find Node.js, replace
"command": "node"with the absolute path fromwhich node.If tools do not refresh after a code change, run MCP: Reset Cached Tools and restart the server.
Use MCP: List Servers >
ucontrol> Show Output to inspect startup errors.For remote SSH/devcontainer workspaces, configure the MCP server in the environment where Node.js and this repo path exist.
Avoid committing real API tokens. Use VS Code
inputsas shown above, or anenvFileoutside source control.
Tool matrix
Tool | Access | HTTP | Endpoint | Destructive |
| read | LOCAL | local | no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| yes |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| yes |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| yes |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| read | GET |
| no |
| write | POST |
| no |
| read | GET |
| no |
| read | GET |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| no |
| write | POST |
| yes |
| write | POST |
| yes |
| write | POST |
| no |
Notes on documented edge cases
ucontrol_read_asset_tagspreserves the vendor-documentedGETrequest with a JSON body. Nativefetchdisallows GET bodies, so the client uses Node's HTTP client for that path.ucontrol_write_umap_populatesendsContent-Type: text/plainwith a JSON string body shaped as{ "data": [...] }, matching the uMap document.Query values that accept multiple IDs can be passed either as a comma-separated string or as an array; arrays are serialized as comma-separated values.
ucontrol_write_umap_model_modifykeeps the vendor warning in the tool description: omitted optional values may wipe existing values.
Development
npm run build
npm testThe test suite starts a local loopback HTTP server. In restricted sandboxes, that may require approval.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/codefitz/ucontrol-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server