KitwireDocs

How Kitwire works

Two kits that fit together: an MCP server that puts your tools in every AI client, and an always-on agent on a Raspberry Pi that uses them while you are away.

The picture

While you work

Your AI clients

Claude Code, Cursor, VS Code and other MCP clients call your tools while you work.

Kit 1

Your MCP server

Your API, database or internal tools, exposed as MCP tools. Runs on Cloudflare Workers, Vercel, Node, Docker or a Pi.

Kit 2 · around the clock

Your Pi agent

OpenClaw on a Raspberry Pi. You talk to it on Telegram or WhatsApp; it runs scheduled jobs and can call the same tools.

What each piece does

The MCP server is the part you write once. Each tool is a small TypeScript function: look something up in your database, call your API, create a record. The Model Context Protocol (MCP) is the standard that AI clients use to discover and call tools like these, so one server works with every client that speaks it.

The Pi agent is an assistant that keeps running when your laptop is closed. It remembers what you tell it, sends you a morning brief, watches your websites and the Pi itself, and answers when you message it. Guide 7 of the Pi kit connects it to your MCP server, so it can use your own tools too.

Which kit do I need?

You want toGet
Connect your product, API or data to Claude, Cursor and other AI clientsMCP Server Starter Kit
Run an always-on assistant on your own hardware that you message from your phonePi Agent Kit
Both, with the agent using your own toolsThe bundle

The MCP kit does not need a Raspberry Pi. The Pi kit does not need the MCP kit, but the two are designed to work together.

Where the AI actually runs

Neither kit runs a language model on your hardware. The thinking happens at the model provider you choose, such as Anthropic or OpenAI:

  • Your MCP server only runs your tools. The AI client's model decides when to call them.
  • Your Pi runs the OpenClaw gateway: the always-on process that holds memory, schedules jobs, talks to Telegram or WhatsApp and calls the model provider's API. That is why a small, quiet board is enough.

You pay the model provider for what you use. The Pi kit keeps background usage low on purpose: health checks are plain scripts, not model calls.

Read next

Get both kits

One-time payment, instant download, free updates for every 1.x release.