@runsnative/mcp-server 0.1.3 → 0.1.5

package/README.md

@@ -2,11 +2,11 @@
 
 RunsNative MCP server — gives any MCP-capable agent access to RunsNative component docs, foundations, design exercises, and theme inference.
 
-Docs content is read from a local checkout of the [runsnative repo](https://github.com/KUKAMANGA-ENTERPRISES/runsnative) via `RUNSNATIVE_CONTENT_ROOT`. A cloud content API (no clone required, updates propagate without reinstalling) is in rollout; once live, the env var becomes optional and the server falls back to the cloud automatically.
+Docs content comes from the RunsNative cloud content API by default — no clone or configuration required, and content updates propagate without reinstalling. Developers working in the [runsnative repo](https://github.com/KUKAMANGA-ENTERPRISES/runsnative) can set `RUNSNATIVE_CONTENT_ROOT` to serve from a local checkout instead.
 
 ## Quick install
 
-Add one block to your MCP client config, pointing `RUNSNATIVE_CONTENT_ROOT` at the `content/` directory of a runsnative checkout.
+Add one block to your MCP client config. No environment configuration is needed.
 
 ### Claude Desktop
 
@@ -18,10 +18,7 @@ Add one block to your MCP client config, pointing `RUNSNATIVE_CONTENT_ROOT` at t
   "mcpServers": {
     "runsnative": {
       "command": "npx",
-      "args": ["-y", "@runsnative/mcp-server"],
-      "env": {
-        "RUNSNATIVE_CONTENT_ROOT": "/path/to/runsnative/content"
-      }
+      "args": ["-y", "@runsnative/mcp-server"]
     }
   }
 }
@@ -36,15 +33,18 @@ Add `.mcp.json` to your project root:
   "mcpServers": {
     "runsnative": {
       "command": "npx",
-      "args": ["-y", "@runsnative/mcp-server"],
-      "env": {
-        "RUNSNATIVE_CONTENT_ROOT": "/path/to/runsnative/content"
-      }
+      "args": ["-y", "@runsnative/mcp-server"]
     }
   }
 }
 ```
 
+To serve from a local checkout instead of the cloud API, add an `env` block:
+
+```json
+"env": { "RUNSNATIVE_CONTENT_ROOT": "/path/to/runsnative/content" }
+```
+
 ## Authoring skill
 
 Once the MCP server is connected, load the RunsNative authoring skill to give your agent full component-authoring guidance. The skill is served at:

package/dist/index.js

@@ -1,3 +1,5 @@
+#!/usr/bin/env node
+import { createRequire } from 'node:module';
 import { Server } from '@modelcontextprotocol/sdk/server/index.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { CallToolRequestSchema, ListToolsRequestSchema, } from '@modelcontextprotocol/sdk/types.js';
@@ -21,7 +23,12 @@ const provider = await createProvider();
 if (provider instanceof RemoteContentProvider) {
     await provider.initialize();
 }
-const server = new Server({ name: 'runsnative-mcp', version: '0.3.0' }, { capabilities: { tools: {} } });
+// Advertised version reads package.json at runtime — a literal here drifts
+// the moment the next release forgets to update it (0.3.0 survived four
+// releases; 0.1.4 outlived its release within hours).
+const require = createRequire(import.meta.url);
+const { version: pkgVersion } = require('../package.json');
+const server = new Server({ name: 'runsnative-mcp', version: pkgVersion }, { capabilities: { tools: {} } });
 server.setRequestHandler(ListToolsRequestSchema, async () => ({
     tools: [
         GET_COMPONENT_TOOL,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@runsnative/mcp-server",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "type": "module",
   "files": [
     "dist/"