tidee-mcp 1.0.1 → 1.1.0

package/README.md

@@ -14,9 +14,16 @@ you to approve it in the browser, and that is the whole setup. In Claude
 Code that is one line:
 
 ```sh
-claude mcp add --transport http tidee https://app.tidee.com/mcp
+claude mcp add --scope user --transport http tidee https://app.tidee.com/mcp
 ```
 
+`--scope user` matters: without it the server is only registered for the
+directory the command ran in, and a session started anywhere else does
+not see it. Then `/mcp` → tidee → Authenticate.
+
+Full setup instructions, including Claude on the web and desktop:
+[tidee.com/en/help/connect-an-assistant](https://tidee.com/en/help/connect-an-assistant/).
+
 **This package** — a local server over stdio, for clients that do not
 speak HTTP MCP, or when you want to point at a development server. It
 needs Node and a token you paste into a config file.
@@ -67,6 +74,9 @@ pnpm run mcp:release                   # from the repo root
 cd packages/tidee-life-mcp && npm publish
 ```
 
+Then push. The `mcp:registry` CI job lists the new version in the MCP
+registry on the next master pipeline — see below.
+
 `mcp:release` bumps the patch version and records a fingerprint of
 everything that determines what gets published — this package's source,
 `tidee-life-core/mcp`, and the runtime dependencies. CI verifies that
@@ -109,16 +119,31 @@ publishing to the registry, not after.
 
 The `com.tidee/` namespace needs DNS authentication (a TXT record on
 tidee.com) rather than the GitHub flow, so that a listing carries the
-product's own name rather than a personal account's:
+product's own name rather than a personal account's.
+
+Publishing is automated. The `mcp:registry` job runs on every master
+pipeline, runs `scripts/mcp-registry-publish.mjs`, and publishes only
+when the registry does not yet have the version in `server.json`. It needs
+the `MCP_REGISTRY_PRIVATE_KEY` CI/CD variable: the hex Ed25519 private
+key whose public half is the `v=MCPv1` TXT record on tidee.com.
+
+Because the registry checks `mcpName` in the npm tarball, the job fails
+(as a warning, not a blocked pipeline) if `server.json` is ahead of npm.
+That means `npm publish` was forgotten; publish, and the next master
+pipeline catches up.
+
+To publish by hand instead:
 
 ```sh
 brew install mcp-publisher
-mcp-publisher login dns --domain tidee.com
+mcp-publisher login dns --domain tidee.com --private-key <hex key>
 mcp-publisher publish
 ```
 
-The registry is in preview and warns about breaking changes, so check
-the current docs at modelcontextprotocol.io/registry before running it.
+The registry is in preview and warns about breaking changes. If the job
+starts failing on a CLI change, check the current docs at
+modelcontextprotocol.io/registry and bump `MCP_PUBLISHER_VERSION` and
+`MCP_PUBLISHER_SHA256` in `.gitlab-ci.yml`.
 
 ## Building
 

package/dist/index.js

@@ -207,6 +207,52 @@ var OAUTH_REGISTRATION_WINDOW_MS = 60 * 60 * 1e3;
 // ../tidee-life-config/dist/src/index.js
 var ALLOWED_PRIORITIZABLE_TYPES = [ITEM_TYPES.todoText.name];
 
+// ../tidee-life-core/dist/src/paths/index.js
+var paths = {
+  // Phase 4 slice F2b — the OAuth consent screen. Under /app because
+  // approving a grant needs a signed-in user; the signed request the
+  // authorize endpoint issues travels in `?request=`.
+  authorize: () => "/app/authorize",
+  activateAccount: (confirmHash) => confirmHash ? `/activate-account/${confirmHash}` : "/activate-account",
+  workspace: () => "/app/workspace",
+  forgot: () => "/forgot",
+  forgotSuccess: () => "/forgot/success",
+  // Phase 3 slice S — landing page for item-share invites. The hash
+  // is the ItemShareInvite.inviteHash carried in the recipient's
+  // email; the page decides which of the three branches to render
+  // (unauth signup CTAs / silent claim / add-and-verify) based on
+  // the caller's auth state and verifiedEmails set.
+  shareInvite: (inviteHash) => inviteHash ? `/invite/${inviteHash}` : "/invite",
+  loggedInRoot: () => "/app",
+  /**
+   * Phase 4 slice M — a link straight to one item.
+   *
+   * A query parameter on the workspace rather than a route of its own,
+   * because the destination IS the workspace: the item is opened in
+   * its box, in place, exactly as clicking it from the sidebar would.
+   * A dedicated route would have to reproduce that, and would leave
+   * the user somewhere the app has no other way of reaching.
+   *
+   * Used by the confirmations external surfaces send back — Slack and
+   * MCP — where the thing captured is otherwise out of sight.
+   */
+  workspaceItem: (itemShareId) => itemShareId ? `/app/workspace?item=${encodeURIComponent(itemShareId)}` : "/app/workspace",
+  login: () => "/login",
+  logout: () => "/app/logout",
+  notLoggedInRoot: () => "/",
+  organiser: () => "/app/organiser",
+  prioritized: () => "/app/prioritized",
+  backlog: () => "/app/backlog",
+  passwordReset: ({ passwordResetHash = null } = {}) => passwordResetHash ? `/password-reset/${passwordResetHash}` : "/password-reset",
+  passwordResetSuccess: () => "/password-reset-success",
+  resendActivationLink: () => "/resend-activation-link",
+  resendActivationLinkSuccess: () => "/resend-activation-link-success",
+  shares: () => "/app/shares",
+  signup: (organisationInviteHash) => organisationInviteHash ? `/signup/${organisationInviteHash}` : "/signup",
+  signupSuccess: () => "/signup/success",
+  verifyEmail: (token) => token ? `/app/verify-email/${token}` : "/app/verify-email"
+};
+
 // ../tidee-life-core/dist/src/mcp/tools.js
 var describeToolError = (failure) => {
   const { code, status, message } = failure ?? {};
@@ -225,6 +271,11 @@ var describeToolError = (failure) => {
     return `tidee returned ${status}.`;
   return message || "The request to tidee failed.";
 };
+var itemUrl = (api2, itemShareId) => {
+  if (!api2.appBaseUrl || !itemShareId)
+    return null;
+  return `${api2.appBaseUrl.replace(/\/+$/, "")}${paths.workspaceItem(itemShareId)}`;
+};
 var tool = (spec) => spec;
 var TIDEE_TOOLS = [
   tool({
@@ -241,10 +292,14 @@ var TIDEE_TOOLS = [
     },
     async run(api2, { text, parentId }) {
       const data = await api2.capture({ text, parentId });
-      const titles = (data.created ?? []).map((c) => c.title);
-      if (titles.length === 0)
+      const created = data.created ?? [];
+      if (created.length === 0)
         return "Nothing was created.";
-      const quoted = titles.map((t) => `"${t}"`).join(", ");
+      const titles = created.map((c) => c.title);
+      const quoted = created.map((c) => {
+        const url = itemUrl(api2, c.itemShareId);
+        return url ? `"${c.title}" (${url})` : `"${c.title}"`;
+      }).join(", ");
       if (data.usedFallback) {
         return `Saved as one item: ${quoted}. tidee could not split that into separate items, so it kept the text as given.`;
       }
@@ -372,6 +427,9 @@ var call = async (path, init) => {
   return body;
 };
 var api = {
+  // The API host and the app host are the same deployment, so the
+  // token's server is also where its items can be looked at.
+  appBaseUrl: API_URL,
   capture: ({ text, parentId }) => call("/api/v1/capture", {
     method: "POST",
     body: { text, parentId }

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "tidee-mcp",
-	"version": "1.0.1",
+	"version": "1.1.0",
 	"mcpName": "com.tidee/tidee",
 	"description": "MCP server for tidee — let an assistant add items to your workspace, read what is there, and mark things done.",
 	"keywords": [