tidee-mcp 1.0.2 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,9 +14,16 @@ you to approve it in the browser, and that is the whole setup. In Claude
|
|
|
14
14
|
Code that is one line:
|
|
15
15
|
|
|
16
16
|
```sh
|
|
17
|
-
claude mcp add --transport http tidee https://app.tidee.com/mcp
|
|
17
|
+
claude mcp add --scope user --transport http tidee https://app.tidee.com/mcp
|
|
18
18
|
```
|
|
19
19
|
|
|
20
|
+
`--scope user` matters: without it the server is only registered for the
|
|
21
|
+
directory the command ran in, and a session started anywhere else does
|
|
22
|
+
not see it. Then `/mcp` → tidee → Authenticate.
|
|
23
|
+
|
|
24
|
+
Full setup instructions, including Claude on the web and desktop:
|
|
25
|
+
[tidee.com/en/help/connect-an-assistant](https://tidee.com/en/help/connect-an-assistant/).
|
|
26
|
+
|
|
20
27
|
**This package** — a local server over stdio, for clients that do not
|
|
21
28
|
speak HTTP MCP, or when you want to point at a development server. It
|
|
22
29
|
needs Node and a token you paste into a config file.
|
|
@@ -67,6 +74,9 @@ pnpm run mcp:release # from the repo root
|
|
|
67
74
|
cd packages/tidee-life-mcp && npm publish
|
|
68
75
|
```
|
|
69
76
|
|
|
77
|
+
Then push. The `mcp:registry` CI job lists the new version in the MCP
|
|
78
|
+
registry on the next master pipeline — see below.
|
|
79
|
+
|
|
70
80
|
`mcp:release` bumps the patch version and records a fingerprint of
|
|
71
81
|
everything that determines what gets published — this package's source,
|
|
72
82
|
`tidee-life-core/mcp`, and the runtime dependencies. CI verifies that
|
|
@@ -109,16 +119,31 @@ publishing to the registry, not after.
|
|
|
109
119
|
|
|
110
120
|
The `com.tidee/` namespace needs DNS authentication (a TXT record on
|
|
111
121
|
tidee.com) rather than the GitHub flow, so that a listing carries the
|
|
112
|
-
product's own name rather than a personal account's
|
|
122
|
+
product's own name rather than a personal account's.
|
|
123
|
+
|
|
124
|
+
Publishing is automated. The `mcp:registry` job runs on every master
|
|
125
|
+
pipeline, runs `scripts/mcp-registry-publish.mjs`, and publishes only
|
|
126
|
+
when the registry does not yet have the version in `server.json`. It needs
|
|
127
|
+
the `MCP_REGISTRY_PRIVATE_KEY` CI/CD variable: the hex Ed25519 private
|
|
128
|
+
key whose public half is the `v=MCPv1` TXT record on tidee.com.
|
|
129
|
+
|
|
130
|
+
Because the registry checks `mcpName` in the npm tarball, the job fails
|
|
131
|
+
(as a warning, not a blocked pipeline) if `server.json` is ahead of npm.
|
|
132
|
+
That means `npm publish` was forgotten; publish, and the next master
|
|
133
|
+
pipeline catches up.
|
|
134
|
+
|
|
135
|
+
To publish by hand instead:
|
|
113
136
|
|
|
114
137
|
```sh
|
|
115
138
|
brew install mcp-publisher
|
|
116
|
-
mcp-publisher login dns --domain tidee.com
|
|
139
|
+
mcp-publisher login dns --domain tidee.com --private-key <hex key>
|
|
117
140
|
mcp-publisher publish
|
|
118
141
|
```
|
|
119
142
|
|
|
120
|
-
The registry is in preview and warns about breaking changes
|
|
121
|
-
the current docs at
|
|
143
|
+
The registry is in preview and warns about breaking changes. If the job
|
|
144
|
+
starts failing on a CLI change, check the current docs at
|
|
145
|
+
modelcontextprotocol.io/registry and bump `MCP_PUBLISHER_VERSION` and
|
|
146
|
+
`MCP_PUBLISHER_SHA256` in `.gitlab-ci.yml`.
|
|
122
147
|
|
|
123
148
|
## Building
|
|
124
149
|
|
package/package.json
CHANGED