webos-mcp

An MCP (Model Context Protocol) server that gives Claude deep, persistent knowledge of legacy Palm/HP webOS development — so you don't have to re-teach Claude platform basics every session, and neither does anyone else. This effort compliments the SDK restoration at sdk.webosarchive.org

This covers the original Palm/HP webOS (2009–2012), not LG's webOS TV platform. Maintained in conjunction with the webOS Archive project.

How It Works

Claude needs to be taught webOS once per session — things like how novacom works, what sources.json does, how the Luna service bus operates. Without help, that knowledge disappears when the session ends and has to be re-established the next time.

This package solves that with a two-layer approach:

┌─────────────────────────────────────────────────────┐
│  Layer 1: webos-mcp (this package)                  │
│  Installed once globally. Holds all the curated     │
│  webOS knowledge. Updated centrally via npm.        │
└─────────────────────────────────────────────────────┘
                          +
┌─────────────────────────────────────────────────────┐
│  Layer 2: CLAUDE.md in your project                 │
│  Added once per project. Tells Claude to load the   │
│  MCP knowledge at the start of every session,       │
│  automatically — no slash command to remember.      │
└─────────────────────────────────────────────────────┘

The result: open any webOS project in Claude Code, and Claude already knows the platform. No setup, no /commands to remember, no copy-pasting documentation.

Setup

Step 1 — Install the MCP server (once, globally)

Prerequisites: Node.js 18+, Claude Code CLI

Add the server to your global Claude Code config at ~/.claude/claude_desktop_config.json:

{
  "mcpServers": {
    "webos": {
      "command": "npx",
      "args": ["-y", "webos-mcp"]
    }
  }
}

Restart Claude Code (or run /mcp to reload servers). That's it — the server is now available in every Claude Code session.

Running locally instead of npx?

{
  "mcpServers": {
    "webos": {
      "command": "node",
      "args": ["/path/to/webos-mcp/index.js"]
    }
  }
}

Step 2 — Add a CLAUDE.md to your webOS project (once per project)

Copy templates/CLAUDE.md from this repo into the root of your webOS app and fill in your project details:

curl -o CLAUDE.md https://raw.githubusercontent.com/webosarchive/webos-mcp/main/templates/CLAUDE.md

Then edit it — set your app ID, framework, target devices, and add any project-specific notes Claude should know.

The key part that makes loading automatic is this section in the template:

## Session Setup

At the start of every session, load the full webOS platform context:

    webos://knowledge/all

When Claude opens your project, it reads CLAUDE.md, sees that instruction, fetches the knowledge bundle from the MCP server, and arrives pre-loaded with webOS context — without you doing anything.

Knowledge Included

All files in knowledge/ are auto-discovered and served as webos://knowledge/<filename>. Load everything at once with webos://knowledge/all, or fetch individual topics as needed mid-session.

Core Platform

UI Frameworks

Services & Backend

System Features

Distribution & Packaging

Networking & Portability

Bundle

Also includes prompts:

• webos-session-start — manually prime Claude with full webOS context
• webos-new-app — scaffold a new Mojo or Enyo app

Developer Experience

Once set up, the flow is:

1. Open your webOS project in Claude Code
2. Claude reads CLAUDE.md → fetches webos://knowledge/all automatically
3. Start working — Claude already knows webOS

You can also load specific topics mid-session:

"Read webos://knowledge/sdk-tools before we continue"

Or manually trigger the session prompt if you're starting a webOS session outside a project:

"Use the webos-session-start prompt"

Project-Level Config (alternative to global)

If you only want the MCP server active for webOS projects, use a .mcp.json file in the project root instead of the global config:

{
  "mcpServers": {
    "webos": {
      "command": "npx",
      "args": ["-y", "webos-mcp"]
    }
  }
}

Keeping Knowledge Current

The knowledge lives in knowledge/ as plain Markdown files — easy to read, easy to edit, easy to contribute to.

To improve or correct anything:

1. Edit the relevant .md file in knowledge/
2. Submit a PR to webosarchive/webos-mcp
3. When a new version is published to npm, everyone using npx gets it automatically on their next session

License

MIT