How to control IT assets with Claude + Handoff MCP

Tiago Yonamine — Fri, 22 May 2026 12:51:44 +0000

How to control IT assets with Claude + Handoff MCP

The problem nobody wants to admit

Your company has 40 employees and 60 notebooks. You know both numbers. What you don't know is which notebook is with which person, whether the responsibility term was signed, and what needs to come back when someone quits.

The typical "solution" is a Google Sheet that someone updates sometimes, a PDF that lives in an email attachment, and a Slack message on the person's last day: "hey can you return the notebook?"

This costs real money. Notebooks are R$5,000–R$15,000 each. And every offboarding is a gamble.

What Handoff does

Handoff is a SaaS built specifically for this: link equipment to people, generate digital responsibility terms, and get a clear offboarding checklist when someone leaves.

The interesting part for developers: it has a native MCP server.

Connecting Handoff to Claude

Add this to your Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "handoff": {
      "url": "https://app.usehandoff.com.br/api/mcp",
      "headers": {
        "Authorization": "Bearer hoff_your_key_here"
      }
    }
  }
}

Get your API key at: Admin → API Keys inside the app.

That's it. No local server to run, no Docker, no Python environment. The MCP server is hosted at app.usehandoff.com.br/api/mcp and speaks JSON-RPC 2.0.

What you can do from Claude

Once connected, you can ask things like:

"Who has the company laptops right now?"

Claude calls list_allocations({ status: "ativa" }) and list_assets({ status: "em_uso" }) and gives you a human-readable summary.

"Fernanda is leaving next week. What does she need to return?"

Claude calls get_employee + list_allocations({ colaboradorId }) and lists every active allocation with delivery dates.

"Register that João Silva joined the team. He's in the TI department and starts 2026-06-01."

Claude calls list_departments to find the TI department ID, then create_employee with all the fields — and confirms the creation.

"Which employees were onboarded in the last 3 months and don't have a signed term yet?"

Claude combines list_employees, list_allocations, and offboarding_pending to cross-reference data.

Available tools

Tool	What it does
`list_employees`	Search employees by name, CPF, or department
`get_employee`	Get one employee with their active allocations
`create_employee`	Register a new employee
`delete_employee`	Archive an employee (blocked if assets are still assigned)
`list_assets`	List assets, filter by status or search term
`get_asset`	Get one asset with allocation history
`create_asset`	Register a new asset
`list_allocations`	List allocations, filter by status or employee
`create_allocation`	Assign an asset to an employee (generates responsibility term)
`return_asset`	Register an asset return (closes the allocation)
`list_departments`	List departments
`list_equipment_types`	List equipment types
`offboarding_pending`	List dismissed employees with pending returns

A real workflow: onboarding + equipment delivery

Here's what happens when you tell Claude:

"Register a new employee: Ana Costa, CPF 123.456.789-00, ana@company.com, Engineer, starting 2026-06-01, TI department. Then allocate the MacBook Pro NB-042 to her."

Claude will:

Call list_departments → find TI department ID
Call create_employee with all fields → get employee ID
Call list_assets({ q: "NB-042" }) → find the asset ID
Call create_allocation → link asset to employee
Return the responsibility term link (termoAceiteUrl) — send this to Ana so she can sign on her phone, no login required

The entire flow in one prompt, zero context switching.

Why this matters beyond convenience

The MCP integration isn't just a party trick. It enables:

HRIS sync via Claude agents: an agent that monitors your HR system and registers new employees in Handoff automatically
Offboarding automation: a workflow that checks offboarding_pending daily and sends reminders
Audit queries: "show me all assets that have never had a signed term" — Claude combines multiple tools and reasons over the data
Natural language search: instead of filtering a table, just describe what you're looking for

Free tier

Handoff has a permanent free tier: unlimited assets, up to 10 employees, no credit card required.

If you want to test the MCP today:

Create a free account at app.usehandoff.com.br/signup
Go to Admin → API Keys → generate a key
Add the config to Claude Desktop
Ask Claude: "list my employees in Handoff"

The bigger picture

As AI agents become more capable, the tools they connect to need clean, well-scoped APIs. Handoff's MCP server is designed for exactly this: a narrow domain (equipment per person), clear data model, and operations that make sense to an agent (create, list, allocate, return, offboard).

If you're building HR/IT automation with Claude and your company is in Brazil, this is probably the fastest path to structured equipment control without standing up your own infrastructure.

Handoff is built in Brazil for Brazilian companies. The UI is in Portuguese, the API field names are in Portuguese, and the responsibility terms are legally valid in Brazil. The MCP protocol and API keys work the same way regardless of language.

DEV Community: Tiago Yonamine

How to control IT assets with Claude + Handoff MCP

How to control IT assets with Claude + Handoff MCP

The problem nobody wants to admit

What Handoff does

Connecting Handoff to Claude

What you can do from Claude

Available tools

A real workflow: onboarding + equipment delivery

Why this matters beyond convenience

Free tier

The bigger picture