fenix-claude-plugin 0.1.3 → 0.2.0

package/.claude-plugin/plugin.json

@@ -1,13 +1,13 @@
-{
-  "name": "fenix",
-  "version": "0.1.3",
-  "description": "Fenix patent automation for Claude — MCP connector plus patent drafting, office-action, and project skills. Provide one API key; the server infers your firm (client + database).",
-  "author": {
-    "name": "Fenix AI",
-    "url": "https://fenix.ai"
-  },
-  "homepage": "https://claude.fenix.ai",
-  "keywords": ["patent", "legal", "fenix", "mcp", "drafting"],
-  "skills": "./skills/",
-  "mcpServers": "./.mcp.json"
-}
+{
+  "name": "fenix",
+  "version": "0.2.0",
+  "description": "Fenix patent automation for Claude — tenant-aware MCP connector, Fenix Workspace, and current patent skills. Use a personal Fenix access code.",
+  "author": {
+    "name": "Fenix AI",
+    "url": "https://fenix.ai"
+  },
+  "homepage": "https://claude.fenix.ai",
+  "keywords": ["patent", "legal", "fenix", "mcp", "drafting"],
+  "skills": "./skills/",
+  "mcpServers": "./.mcp.json"
+}

package/.mcp.json

@@ -1,11 +1,11 @@
-{
-  "mcpServers": {
-    "fenix": {
-      "type": "http",
-      "url": "https://claude.fenix.ai/api/plugin",
-      "headers": {
-        "Authorization": "Bearer ${FENIX_API_KEY:-NOT_SET}"
-      }
-    }
-  }
-}
+{
+  "mcpServers": {
+    "fenix": {
+      "type": "http",
+      "url": "https://claude.fenix.ai/chau/mcp",
+      "headers": {
+        "Authorization": "Bearer ${FENIX_MCP_TOKEN:-NOT_SET}"
+      }
+    }
+  }
+}

package/README.md

@@ -1,55 +1,48 @@
-# Fenix plugin for Claude
+# Fenix plugin for Claude Code
 
-Patent automation for Claude Code / Cowork. Bundles:
+The Fenix plugin connects Claude Code to the current tenant-aware Fenix MCP
+server and bundles the current patent skills plus the Fenix Workspace.
 
-- **The Fenix MCP connector** — `https://claude.fenix.ai/api/plugin` (read + draft tools: `get_project`, `save_project`, `print_patent`, `install_fenix_skills`, and more).
-- **The patent skills** — `fenix-application`, `fenix-office-action`, `fenix-project` — shipped as a static snapshot so they work immediately, with a `/fenix-install` command to refresh the firm-customized, latest versions from the server.
+## Connection
 
-## One key, nothing else
+The connector uses `https://claude.fenix.ai/chau/mcp` and authenticates with a
+personal Fenix MCP access code stored in `FENIX_MCP_TOKEN`. Create the code in
+Fenix under **Settings > MCP Access**. The connector exposes two tools:
+`read` and `write`. Call `read({ resource: "schema" })` to discover the
+available resources.
 
-You provide a **single API key**. The server infers your firm — client *and* database — from that key, so you never configure a database or client name.
+## Install
 
-## Install (no git required)
+```text
+claude plugin marketplace add https://claude.fenix.ai/marketplace.json
+claude plugin install fenix@fenix
+```
 
-The marketplace is served over plain HTTPS and the plugin is distributed via npm,
-so end users never touch git:
+Set the token outside of chat, then reload plugins:
 
-1. Add the marketplace and install the plugin:
-   ```
-   claude plugin marketplace add https://claude.fenix.ai/marketplace.json
-   claude plugin install fenix@fenix
-   ```
-2. Set your key (see `/fenix-setup` for guided steps):
-   - macOS/Linux: `export FENIX_API_KEY="<your key>"` in `~/.zshrc` / `~/.bashrc`
-   - Windows: `setx FENIX_API_KEY "<your key>"`
-   Restart Claude Code so the connector picks up the key.
-3. (Optional) `/fenix-install` — refresh the skills to your firm's latest customized versions.
+```powershell
+setx FENIX_MCP_TOKEN "your-personal-access-code"
+```
 
-> Local/dev install (from a clone of this repo, no npm needed):
-> `claude plugin marketplace add <path-to-Project-Management>` then `claude plugin install fenix@fenix`
-> — this uses the repo-root `.claude-plugin/marketplace.json` (relative source).
+Run `/reload-plugins`, then verify the Fenix server is connected in `/mcp`.
 
-## Publishing a new version (maintainers)
+## Fenix Workspace
 
-The plugin ships to users as the npm package **`fenix-claude-plugin`**, referenced by the
-HTTPS marketplace at `https://claude.fenix.ai/marketplace.json` (served by
-`back-end/pages/api/marketplace.ts`).
+To install the reusable Fenix Workspace, call:
 
-1. Regenerate the bundled snapshot: `cd back-end && npm run gen:snapshot`.
-2. Bump the version in **three** places (keep them identical):
-   - `fenix-plugin/package.json` → `version`
-   - `fenix-plugin/.claude-plugin/plugin.json` → `version`
-   - `back-end/pages/api/marketplace.ts` → `PLUGIN_VERSION`
-3. Publish: `cd fenix-plugin && npm publish` (unscoped public package — no scope/org needed).
-4. Deploy the back-end so `/marketplace.json` and the `/api/plugin` connector are live.
+```text
+read({ resource: "artifacts", name: "fenix-workspace" })
+```
 
-Verify the npm contents before publishing with `npm pack --dry-run`.
+Save and open the returned `fenix-workspace.html` exactly as received from a
+desktop-side session. Do not modify its HTML: it contains the live artifact
+permissions for the Fenix `read` and `write` tools.
 
-## Commands
+## Publishing
 
-- `/fenix-setup` — guided API-key configuration.
-- `/fenix-install` — pull the latest, firm-customized skills from the server.
+Run `npm run gen:snapshot` from `back-end` to rebuild the bundled current skills
+and workspace artifacts. Keep the versions in `fenix-plugin/package.json`,
+`fenix-plugin/.claude-plugin/plugin.json`, and
+`back-end/pages/api/marketplace.ts` identical. Check the package with
+`npm pack --dry-run`, then publish it from `fenix-plugin` with `npm publish`.
 
-## How the skills stay in sync
-
-The bundled `skills/` snapshot is **generated from the same base files the server serves** (`back-end/skills/…`) — it is never hand-edited. Editing a base file and regenerating updates both the server's dynamic install and this static snapshot, so the two never drift. See `back-end/skills/README.md` for the source of truth and the regeneration script.