A side-by-side look at the Arcnm and Kiln MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Arcnm for industrial & iot work over a hosted endpoint; choose Kiln for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
A
Choose Arcnm when
You need dedicated capabilities in the Industrial & IoT domain.
No tool names declared yet. Check the project README from the listing page.
Kiln tools 5
load_filament
unload_filament
plan_only
plate_clear
look_at_plate
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Arcnm is categorized under Industrial & IoT and uses a remote HTTP/SSE transport. Kiln belongs to Industrial & IoT and uses a local stdio subprocess. Pick Arcnm for industrial & iot work and Kiln for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Arcnm has no declared pricing — check the project's own site. Auth: no auth required. Kiln is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add arcnm and codeofaxel-kiln as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Arcnm has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Kiln has 64/100 (Good) with 4 views, 0 installs and 92 GitHub stars.