
by DeviceShelf
DeviceShelf MCP lets an AI assistant answer questions about your network from the live inventory and monitoring data in your own DeviceShelf Server. It is local, read-only by default and off until you enable it.
PluginContact for pricing
Step 1: Install DeviceShelf Server using Docker, the .deb package, the macOS package or the Windows installer.
Step 2: Set DEVICESHELF_MCP_ENABLE=true in the server environment file and restart the server.
Step 3: Connect your AI client to http://<your-server>:8088/mcp with the bearer token; Claude Desktop can bridge to it with mcp-remote.
Step 4: Ask questions such as what is online, what changed since yesterday, or which certificates expire soon.
Step 5: Optionally set DEVICESHELF_MCP_ALLOW_ACTIONS=true to let the assistant make changes.
The endpoint is strictly local and there is no DeviceShelf cloud connector. Data goes to an external service only through the AI client you connect.
Not by default. Action tools need a separate opt-in setting, and an optional confirmation setting asks you before impactful actions.
No. You enable it with DEVICESHELF_MCP_ENABLE=true and restart the server.
Requirements
Q-Ring MCPq-ring stores API keys and other secrets in your operating system's native keychain and exposes them to AI coding agents over MCP. It also ships a command-line tool for managing the same secrets.Stamp MCPStamp is an MCP server of small tools agents use often: NTP time and clock drift, UUIDs, diffs, safe arithmetic, and tamper-evident attestation. It runs locally over stdio or as a hosted public endpoint.NetDiag MCPNetDiag MCP is an MCP server that runs network diagnostics on request: DNS, ping, path reports, port checks, HTTP and TLS checks, and WHOIS. It helps triage reports like "can't reach X" without opening a shell on a jump host.