hackshop
dev.hackshopv0.0.6Updated Oct 4, 2026
Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.
Overview
AI-generated overview
Lets an assistant plan a physical hardware build for an AI agent, including boards, parts list, assembly and pairing.
- What it does
- This server gives an assistant tools for planning and building a physical body for an AI agent. According to the registry description, it covers boards, a parts list, assembly and pairing. The manifest does not list individual tool names, so the exact tool set is not documented here.
- When to use it
- Worth considering when you want an assistant to help choose hardware boards and components and work through assembly and pairing steps for a physical agent build. It is not aimed at software-only projects.
- Requirements
- Available as a remote endpoint and as a local npm package (hackshop-mcp) over stdio, so the local option needs Node.js. No authentication is declared. An optional ANTHROPIC_API_KEY can improve propose_hardware when the MCP host cannot sample. Network access is needed for the remote endpoint.
Before you install
The optional ANTHROPIC_API_KEY is a secret and should be supplied only if you accept sending requests to that provider. Anonymous usage pings are on by default; set HACKSHOP_TELEMETRY to 0 to turn them off. The manifest lists no tools, so review what the server can do before installing.
Installation
In SourceWeft
- Open hackshop in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"hackshop-mcp": {
"type": "http",
"url": "https://www.hackshop.dev/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.0.6LatestOct 4, 2026
