@dropthis/mcp - npm Package Compare versions

Comparing version

+1

-1

package.json

		{
		"name": "@dropthis/mcp",
		"version": "0.34.1",
		"version": "0.35.0",
		"description": "Official MCP server for dropthis — publish content and get a permanent URL from any MCP-compatible agent.",
		@@ -5,0 +5,0 @@ "license": "MIT",

+4

-2

README.md

		@@ -96,6 +96,8 @@ <p align="center"><img src="https://dropthis.app/icon-512.png" width="76" height="76" alt="dropthis" /></p>
		- `dropthis_use_workspace` switches the active workspace; the choice persists server-side across reconnects.
		- `dropthis_publish` (and `dropthis_update_content`) take a per-call `workspace` override to publish into a different workspace without switching the active one.
		- `dropthis_publish` takes a per-call `workspace` override — write-side targeting for a new drop.
		- `dropthis_list` takes a per-call `workspace` selector — list another workspace you belong to without switching.
		- id-addressed ops (`update_content`, `update_settings`, `delete`, …) always act in the drop's own workspace (a drop never moves workspace).
		- `dropthis_account` echoes the active workspace (name, kind, your role).

		A static `sk_` API key is pinned to the one workspace it was minted in — `dropthis_use_workspace` and the per-publish `workspace` override do not apply to it. To act in another workspace with an `sk_` key, mint a key in that workspace. OAuth (remote) connections are not pinned and can switch freely.
		A static `sk_` API key is pinned to the one workspace it was minted in — `dropthis_use_workspace` and the per-call `workspace` override/selector do not apply to it. To act in another workspace with an `sk_` key, mint a key in that workspace. OAuth (remote) connections are not pinned and can switch freely.

		@@ -102,0 +104,0 @@ ### Permissions & read-only

dist/bin.cjs

Sorry, the diff of this file is too big to display

dist/bin.cjs.map

Sorry, the diff of this file is too big to display

New alerts