Agents Index

hackshop

Online

Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.

Visit publisherConnectJSON

What it can do: 10 tools

  • intake_gadget read-onlyReturn four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.
  • plan_gadget read-onlyDeterministically plan a physical body for an AI agent using Meta Muse boards. Partial intake answers produce remaining questions and an intake completion status. Inputs: `idea` 3-2000 chars (optional when `answers` or `
  • get_build_plan read-onlyReturn the complete deterministic build plan for a catalog device id: difficulty, board-specific flash warnings, parts, shopping list with buy_options, prices checked date and purchase policy, steps, machine-readable ass
  • assess_hackability read-onlyLook up a device by id, exact name or substring and return hackability, brick risk, firmware links, curated firmware playbooks, community size, build page and agent platform support. Input: `device_name` 1-200 chars.
  • find_reverse_engineering_examples read-onlySearch Hackshop's curated hardware reverse-engineering examples and research methods. With no query, returns the newest dated examples first. Evidence labels distinguish reproduced work, documented implementations, autho
  • find_firmware_playbooks read-onlyFind curated owner-authorized firmware, local-protocol and cloud-replacement playbooks. Results rank less-invasive paths first and contain research guidance rather than device compatibility approval.
  • check_firmware_compatibility read-onlyFail-closed compatibility check for one firmware playbook. Required model, codename, revision, SoC or firmware identifiers must exactly match a curated target; missing facts return unknown and mismatches return unsupport
  • get_firmware_playbook read-onlyReturn a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.
  • verify_firmware_artifact read-onlyCompare a caller-supplied filename, source URL and SHA-256 with Hackshop's curated metadata. Hackshop does not fetch, upload or redistribute the artifact; absent hashes return unknown.
  • prepare_firmware_job read-onlyPrepare a non-executing firmware manifest after owner authorization and an exact compatibility match. Returns backup, recovery, sources, validation and stop points; never returns a flash command.

Connect it

Claude Code
claude mcp add --transport http hackshop https://www.hackshop.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://www.hackshop.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "hackshop": {
      "url": "https://www.hackshop.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "hackshop": {
      "type": "http",
      "url": "https://www.hackshop.dev/mcp"
    }
  }
}

Questions

What does hackshop do?

Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing. It exposes 10 tools to AI assistants.

What tools does hackshop provide?

10 tools, including intake_gadget, plan_gadget, get_build_plan, assess_hackability, find_reverse_engineering_examples, find_firmware_playbooks, check_firmware_compatibility, get_firmware_playbook, verify_firmware_artifact, prepare_firmware_job.

How do I connect hackshop to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://www.hackshop.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does hackshop require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is hackshop online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes hackshop?

hackshop.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Agents & Orchestration