Open Mcp Apps MCP server
{
"mcpServers": {
"open-mcp-apps": {
"command": "npx",
"args": [
"-y",
"@2nd1st/open-mcp-apps@latest"
]
}
}
}{
"mcpServers": {
"open-mcp-apps": {
"command": "npx",
"args": [
"-y",
"@2nd1st/open-mcp-apps@latest"
]
}
}
}{
"mcpServers": {
"open-mcp-apps": {
"command": "npx",
"args": [
"-y",
"@2nd1st/open-mcp-apps@latest"
]
}
}
}{
"servers": {
"open-mcp-apps": {
"command": "npx",
"args": [
"-y",
"@2nd1st/open-mcp-apps@latest"
]
}
}
}{
"mcpServers": {
"open-mcp-apps": {
"command": "npx",
"args": [
"-y",
"@2nd1st/open-mcp-apps@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @2nd1st/open-mcp-appsversion 0.5.9
What it does
open-mcp-apps is an MCP server that lets AI assistants build and persist interactive HTML applications with data storage. The AI writes single-file apps once, which are saved to a registry and reusable across conversations. It serves these apps via a local `ui://` protocol with SQLite-backed data persistence and versioning.
- Have an AI create a custom interactive tool (calculator, tracker, planner) that you can reuse in future conversations by name.
- Store and edit structured data (lists, forms, records) where both you and the AI can make changes with conflict resolution and idempotency.
- Build UI-driven workflows where the AI generates and maintains the interface code while the engine handles persistence, theming, and protocol details.
Tools this server exposes
| Tool | Does |
|---|---|
| app_create | Create a new app from HTML code and register it with a name. |
| app_list | List all registered apps in the registry. |
| app_open | Open a registered app by name. |
| collection_write | Write data to a named collection with versioning and idempotent commands. |
| collection_read | Read items from a named collection. |
| collection_query | Query a collection with filtering and sorting. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.