diff --git a/DIRECTORY-EDITION.md b/DIRECTORY-EDITION.md new file mode 100644 index 0000000..41e7782 --- /dev/null +++ b/DIRECTORY-EDITION.md @@ -0,0 +1,32 @@ +# Claude plugin directory edition + +This branch (`Claude`) is the version of the Deepnote plugin that the Claude plugin directory tracks. It is `main` with a few items removed. Do not merge it into `main`. + +## Why it exists + +The directory accepts scripts, file types outside its allowed list, and extra config fields only from Verified organizations. Deepnote's Claude organization is not Verified, so the directory refused the plugin as it is on `main`. `main` stays unchanged for Codex and for the Claude Code marketplace in this repository. + +## How it differs from main + +All differences are inside `plugins/deepnote/`, the only folder the directory reads: + +- `skills/deepnote-data-apps/scripts/app-dev.mjs` is removed. The directory does not accept scripts. +- `assets/deepnote-icon.svg` is removed. SVG is not an allowed image type. The listing uses `assets/icon.png`. +- `.codex-plugin/plugin.json` is removed. It is not used by Claude and referred to the SVG. +- `.mcp.json` has no `bearer_token_env_var` field. Claude signs in with OAuth. +- `skills/deepnote-data-apps/SKILL.md` has no local preview steps. It tells Claude to say the page was not checked and to ask the user to open it. +- `README.md` in the plugin folder describes this edition. + +The Codex marketplace file in `.agents/` and the root `README.md` are left as they are on `main`. They do not apply to this branch. + +## Updating it for a release + +1. Merge `main` into this branch: `git checkout Claude && git merge main`. +2. Resolve conflicts by keeping this branch's side for the items listed above. A change on `main` to a removed file shows up as a modify/delete conflict; keep the deletion. +3. Check that nothing in `plugins/deepnote/` refers to the removed files: `grep -rn -E "app-dev|scripts/|bearer_token|\.svg" plugins/deepnote`. The one expected match is the `logo.svg` example in the data apps skill. +4. Run `claude plugin validate --strict plugins/deepnote`. +5. Push. The directory scans the new commit and shows the result in the developer portal. + +## Retiring it + +Once the organization is Verified, set the plugin's tracked branch back to `main` on its Settings tab in the developer portal, then delete this branch. diff --git a/plugins/deepnote/.codex-plugin/plugin.json b/plugins/deepnote/.codex-plugin/plugin.json deleted file mode 100644 index 6536296..0000000 --- a/plugins/deepnote/.codex-plugin/plugin.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "name": "deepnote", - "version": "0.9.2", - "description": "Search Deepnote workspaces, inspect and edit projects and notebooks, manage integrations and project machines, build data apps and Streamlit apps, generate links, read docs, and run notebooks from ChatGPT and Codex.", - "author": { - "name": "Deepnote", - "url": "https://deepnote.com" - }, - "homepage": "https://github.com/deepnote/agent-plugins", - "repository": "https://github.com/deepnote/agent-plugins", - "license": "Apache-2.0", - "keywords": [ - "deepnote", - "mcp", - "codex", - "notebooks", - "data", - "analytics" - ], - "skills": "./skills/", - "mcpServers": "./.mcp.json", - "interface": { - "displayName": "Deepnote", - "shortDescription": "Analyze data with Deepnote", - "longDescription": "Work with Deepnote workspaces, projects, and notebooks from ChatGPT and Codex. Search resources, inspect projects, read, write, copy, and delete project files, manage integrations, choose project environments, start, stop, and resize project machines, generate project and notebook links, edit notebook structure, build data apps and Streamlit apps, read Deepnote docs, run notebooks with optional inputs, and summarize run history, status, and outputs. Requires a Deepnote account with access to the workspace and permission for each requested action; a workspace admin must enable MCP access.", - "developerName": "Deepnote", - "category": "Data & Analytics", - "capabilities": [ - "Interactive", - "Read", - "Write" - ], - "websiteURL": "https://deepnote.com", - "supportURL": "https://deepnote.com/docs/support", - "privacyPolicyURL": "https://deepnote.com/privacy", - "termsOfServiceURL": "https://deepnote.com/terms", - "defaultPrompt": [ - "Search my Deepnote workspace.", - "Inspect this Deepnote notebook.", - "Run a Deepnote notebook with inputs." - ], - "brandColor": "#3793EF", - "composerIcon": "./assets/deepnote-icon.svg", - "logo": "./assets/deepnote-icon.svg", - "screenshots": [] - } -} diff --git a/plugins/deepnote/.mcp.json b/plugins/deepnote/.mcp.json index 3b2c284..f6da7ec 100644 --- a/plugins/deepnote/.mcp.json +++ b/plugins/deepnote/.mcp.json @@ -2,8 +2,7 @@ "mcpServers": { "deepnote": { "type": "http", - "url": "https://deepnote.com/mcp", - "bearer_token_env_var": "DEEPNOTE_MCP_TOKEN" + "url": "https://deepnote.com/mcp" } } } diff --git a/plugins/deepnote/README.md b/plugins/deepnote/README.md index e4f1ca8..03a308a 100644 --- a/plugins/deepnote/README.md +++ b/plugins/deepnote/README.md @@ -17,6 +17,8 @@ If you already added the Deepnote connector in Claude, the plugin uses the same Then run `/mcp`, choose the Deepnote server, and sign in. +Installed this way, the plugin also includes a script that previews data apps on your computer before publishing. The directory edition leaves that script out. + ## Requirements - A Deepnote account with access to the workspace you want to use. @@ -35,8 +37,7 @@ Then run `/mcp`, choose the Deepnote server, and sign in. ## Data and network access - The plugin sends requests to `https://deepnote.com/mcp` on your behalf. What Claude reads there, such as notebook content, run outputs, file contents, and integration metadata, becomes part of your conversation with Claude. -- The plugin has no hooks and runs nothing on its own. -- The data apps skill ships one optional script, `skills/deepnote-data-apps/scripts/app-dev.mjs`, which Claude can run to preview a data app page before publishing it. It needs Node 18 or later and uses built-in modules only. It starts two servers on `127.0.0.1` (ports 4747 and 4748 by default), serves the page folder from your computer, and makes no outbound requests itself. The previewed page calls the Deepnote API from your browser with a short-lived viewer token that is passed on the command line and never written to a file. The preview only works where Claude can run local commands. +- The plugin has no hooks, ships no scripts, and runs nothing on your computer. - Data app pages that Claude writes with this skill load the Deepnote app client from `deepnote.com`, the Tailwind CSS browser build from `cdn.jsdelivr.net`, and the Inter font from `fonts.googleapis.com`. ## Links diff --git a/plugins/deepnote/assets/deepnote-icon.svg b/plugins/deepnote/assets/deepnote-icon.svg deleted file mode 100644 index d1f7d31..0000000 --- a/plugins/deepnote/assets/deepnote-icon.svg +++ /dev/null @@ -1,10 +0,0 @@ - diff --git a/plugins/deepnote/skills/deepnote-data-apps/SKILL.md b/plugins/deepnote/skills/deepnote-data-apps/SKILL.md index b8bd5dc..2504230 100644 --- a/plugins/deepnote/skills/deepnote-data-apps/SKILL.md +++ b/plugins/deepnote/skills/deepnote-data-apps/SKILL.md @@ -33,7 +33,7 @@ A data app project has two parts: the page, a responsive HTML page in `_deepnote ## The Page - `index.html` can load other files from `_deepnote_static/` by relative path, such as `styles.css`, `app.js`, or `logo.svg`. Keep the app client script and the Tailwind setup below in `index.html`, and move the rest into files of their own when that keeps the page easier to change. -- Keep a local copy of `_deepnote_static/` in a folder of its own. Read each file the page loads or you will change with `read_file` once, unless you wrote it in this conversation; `get_project` lists them. Images that `read_file` cannot read show as broken in the local preview. Edit the files there, and once the page works in the local preview in Testing, push each new or changed file with `write_file` at its path under `_deepnote_static/` and `overwrite: true`. Where you cannot run local commands, write the files with `write_file` directly. When the app existed before this conversation, ask the user before the first push whether to update it in Deepnote, with the preview URL when there is one: pushing overwrites the app for good, and viewers of a published app see the change at once. Once they agree, push later changes they ask for in this conversation without asking again. +- Read each file the page loads or you will change with `read_file` once, unless you wrote it in this conversation; `get_project` lists them. Write each new or changed file with `write_file` at its path under `_deepnote_static/` and `overwrite: true`. When the app existed before this conversation, ask the user before the first push whether to update it in Deepnote: pushing overwrites the app for good, and viewers of a published app see the change at once. Once they agree, push later changes they ask for in this conversation without asking again. - Start the `
` of `index.html` with ``, before any other script, and load CDN scripts with `crossorigin="anonymous"`. The script exposes `Deepnote.connect()`, not React components or `DeepnoteApp`. - Style the page with Tailwind CSS 4.3.3. After the app client script, add the Tailwind browser build, Inter, and the default theme below, then use its colors in classes (`bg-surface`, `text-muted`, `border-border`, `bg-accent`, `text-positive`, ...). Its dark values apply on their own, so don't add `dark:` variants for theme colors. Chart code reads series colors with `getComputedStyle(document.documentElement).getPropertyValue('--color-chart-1')`. @@ -78,15 +78,7 @@ A data app project has two parts: the page, a responsive HTML page in `_deepnote Test a changed-input submission with `create_run`, its `inputs`, and `detachedRunStorageMode: "readonly"`, then read it with `get_run` and `snapshotDelivery: "blocks"`. When it fails, inspect its status and output and fix the cause; when it is still pending after several checks, point to run history without claiming the flow works. Finish with a run using `{}` and check that it succeeds, since, when the app lets everyone with access see results without running it, they see the latest editor run until they run it themselves. Delete scratch blocks when done. -Preview the page locally before pushing it, against the same API and data it gets in Deepnote: - -1. Mint a viewer token with `create_data_app_token` for the project. Pass it only on the command line; never write it into files or answers. -2. Run `node scripts/app-dev.mjs