Homespun
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http homespun 'https://homespun.dev/mcp'
{
"mcpServers": {
"homespun": {
"type": "http",
"url": "https://homespun.dev/mcp"
}
}
}
@homespunapps/mcpclaude mcp add homespun -e 'HOMESPUN_API_KEY=<your homespun_api_key>' -e 'HOMESPUN_URL=<HOMESPUN_URL>' -e 'HOMESPUN_AGENT_NAME=<HOMESPUN_AGENT_NAME>' -e 'HOMESPUN_REGISTER_SECRET=<your homespun_register_secret>' -- npx -y @homespunapps/mcp@1.6.98
{
"mcpServers": {
"homespun": {
"command": "npx",
"args": [
"-y",
"@homespunapps/mcp@1.6.98"
],
"env": {
"HOMESPUN_API_KEY": "<your homespun_api_key>",
"HOMESPUN_URL": "<HOMESPUN_URL>",
"HOMESPUN_AGENT_NAME": "<HOMESPUN_AGENT_NAME>",
"HOMESPUN_REGISTER_SECRET": "<your homespun_register_secret>"
}
}
}
}
Environment variables
HOMESPUN_API_KEYsecret Homespun agent API key. If unset, the server auto-registers a fresh agent against the relay on first use and saves the key to the shared CLI store (~/.config/homespun/config.json).HOMESPUN_URLHomespun relay base URL. Defaults to the hosted relay https://homespun.dev; set this to point at a different relay.HOMESPUN_AGENT_NAMEDisplay name for the auto-registered agent on the relay.HOMESPUN_REGISTER_SECRETsecret Registration secret, required only for relays running REGISTRATION_MODE=secret.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Homespun
Apps your AI builds and hosts, for you and the people you invite.
An agent creates a real web app from a single HTML file plus a manifest, and Homespun hosts it at a URL. People open the link and use it. No install, no build step, no deploy pipeline.
Docs: docs.homespun.dev
What is in this repository
The client side, all MIT licensed:
| Package | What it is |
|---|---|
@homespunapps/cli | The homespun command line client |
@homespunapps/mcp | The MCP server, so an agent can drive Homespun as a tool |
@homespunapps/core | Shared client library and types |
Plus the agent skill (skills/homespun) and the Claude plugin
(plugins/homespun).
The relay, which is the hosted server these clients talk to, is not open source and is not in this repository.
Getting started
npm install -g @homespunapps/cli
homespun agent register
homespun deploy ./my-app
./my-app needs an index.html and a manifest.json. The
quickstart walks through both.
To use Homespun from a chat client such as Claude or ChatGPT instead of a terminal, see Connect to your AI chat, which needs no install at all.
Reference
Every reference page below is generated from the source it documents, and a test fails the build when the two disagree.
- HTTP API, every
/v1endpoint - CLI, every command and flag
- SDK, the
window.homespunbrowser API - Manifest, the app manifest format
- Errors, every error code
- Agent guide and MCP guide
Contributing
This repository is a read-only mirror. See CONTRIBUTING.md.
License
MIT. See LICENSE.
Frequently asked questions
What is Homespun?
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
How do I install Homespun?
It runs as a remote server. In Claude Code: claude mcp add --transport http homespun 'https://homespun.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Homespun need an API key?
Yes. It expects HOMESPUN_API_KEY, HOMESPUN_REGISTER_SECRET, which you set in its configuration.
Is Homespun open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Homespun?
It is published by homespunapps. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.