Security-first MCP server for TP-Link Omada, with a stdio-first runtime, capability-gated tools, and OpenAPI-based network automation.
Connect Safe Tp Link Omada MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Security-first MCP server for TP-Link Omada, with a stdio-first runtime, capability-gated tools, and OpenAPI-based network automation. The safe tp link omada mcp mcp server is what makes that connection.
Security-focused MCP server for TP-Link Omada Open API workflows.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Task — CommandBuild — npm run buildInspector — Use the MCP Inspector when you want to test the built server interactively:Device — The Device tool exposed by this serverNetwork — The Network tool exposed by this serverConfiguration is passed through the environment: OMADA_BASE_URL, OMADA_CLIENT_ID, OMADA_CLIENT_SECRET, OMADA_OMADAC_ID, OMADA_SITE_ID, MCP_HTTP_PATH, MCP_HTTP_HEALTHCHECK_PATH, MCP_HTTP_NGROK_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Safe Tp Link Omada MCP's toolset — Task, Build, Inspector and 2 more — is a fair guide to whether it matches your workflow. It is maintained by gaspareduard; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Task | Command |
| Build | npm run build |
| Inspector | Use the MCP Inspector when you want to test the built server interactively: |
| Device | The Device tool exposed by this server. |
| Network | The Network tool exposed by this server. |
{
"mcpServers": {
"omada": {
"command": "npx",
"args": ["-y", "npm"],
"env": {
"OMADA_BASE_URL": "your-value",
"OMADA_CLIENT_ID": "your-value",
"OMADA_CLIENT_SECRET": "your-value",
"OMADA_OMADAC_ID": "your-value",
"OMADA_SITE_ID": "your-value",
"MCP_HTTP_PATH": "your-value",
"MCP_HTTP_HEALTHCHECK_PATH": "your-value",
"MCP_HTTP_NGROK_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OMADA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| OMADA_CLIENT_ID | Configuration value read at startup. | Optional |
| OMADA_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| OMADA_OMADAC_ID | Configuration value read at startup. | Optional |
| OMADA_SITE_ID | Configuration value read at startup. | Optional |
| MCP_HTTP_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_HTTP_HEALTHCHECK_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_HTTP_NGROK_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.