Dell, Lenovo and Apple MCP

Dell, Lenovo and Apple + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Dell, Lenovo and Apple

API. Not affiliated with, endorsed by, or sponsored by Dell Inc., Lenovo and Apple Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Dell, Lenovo and Apple warranty end dates for every client's devices, in one local mirror. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

For ChatGPT, run warranty-mcp --transport http with WARRANTY_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Dell, Lenovo and Apple MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Dell, Lenovo and Apple release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install warranty@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Dell, Lenovo and Apple Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.ps1 | iex. Then authenticate per the README and run warranty-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.sh)

The installer drops both warranty-cli (the CLI) and warranty-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

warranty-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/warranty/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update warranty@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/warranty --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/warranty --force

Hermes speaks MCP natively, so it can also use the warranty-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the warranty skill from https://github.com/servosity/msp-skills/tree/main/skills/warranty. The skill defines how its required CLI (warranty-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Every vendor is optional: set the ones you have, then run doctor.

macOS / Linux:

export WARRANTY_DELL_CLIENT_ID=<client id> WARRANTY_DELL_CLIENT_SECRET=<client secret>   # Dell TechDirect

export WARRANTY_LENOVO_CLIENT_KEY= # Lenovo eSupport export WARRANTY_APPLE_CLIENT_ID= WARRANTY_APPLE_KEY_ID= WARRANTY_APPLE_PRIVATE_KEY=~/keys/apple-business.pem # Apple Business warranty-cli doctor --json

Windows (PowerShell):

$env:WARRANTY_DELL_CLIENT_ID = "<client id>"; $env:WARRANTY_DELL_CLIENT_SECRET = "<client secret>"

$env:WARRANTY_LENOVO_CLIENT_KEY = " " $env:WARRANTY_APPLE_CLIENT_ID = " "; $env:WARRANTY_APPLE_KEY_ID = " "; $env:WARRANTY_APPLE_PRIVATE_KEY = "$HOME\keys\apple-business.pem" warranty-cli doctor --json

doctor --json lists each vendor under vendors with what it still needs, without printing any value. With a Dell credential it spends one read of Dell's entitlement endpoint (service tag 0000000) and reports whether Dell accepted it. It does not prove a Lenovo or Apple key works: run a lookup for that. Dell credentials can also be stored with warranty-cli auth login.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Warranty lookups are usually one serial in one vendor portal, or an API wrapper that forwards each question as one live call. That's fine for one device. It dies at scale, when you're asking "which devices across all 40 clients lose coverage before the end of next quarter, from Dell, Lenovo and Apple at once?"

This skill keeps every answer in a local warranty mirror per client. Fleet questions become one local query: instant, offline, and the AI sees the answer, not the raw data. report, lifecycle and unresolved join devices, clients and coverage lines from all three vendors - work a stateless API wrapper can't do.

The pain this closes

Dell's own community has asked for years for a bulk answer: "Is there an easy way to enter multiple service tags to check the warranty status on all of my hardware?" (Dell Community, May 2022; one reply had over 1,000 computers to check). For an MSP the question repeats per client and per vendor, in three portals with three credentials.

• warranty-cli import devices.csv --customer "Acme Dental" - load an RMM export under the client's name.
• warranty-cli lookup --file devices.csv --customer "Acme Dental" - every serial, with whichever vendor credentials you have.
• warranty-cli report --within 90d - expired and expiring devices per client, offline.
• warranty-cli lifecycle --quarters 4 - coverage endings by quarter for refresh planning.
• warranty-cli unresolved - what could not be verified, each with one reason.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, on Plus, Pro, Team, Business, Enterprise, and Education plans (Free tier does not yet expose Developer Mode). ChatGPT connects to remote MCP servers over HTTPS, not local stdio binaries. The Dell, Lenovo and Apple MCP server runs locally over stdio by default