groovehq-mcp 0.2.0 → 0.3.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 +12 -0
- package/dist/index.js +7 -905
- package/dist/index.js.map +1 -1
- package/dist/server.d.ts +11 -0
- package/dist/server.d.ts.map +1 -0
- package/dist/server.js +914 -0
- package/dist/server.js.map +1 -0
- package/dist/tools/drafts.d.ts +1 -1
- package/dist/tools/drafts.d.ts.map +1 -1
- package/dist/tools/drafts.js +7 -2
- package/dist/tools/drafts.js.map +1 -1
- package/package.json +11 -1
package/README.md
CHANGED
|
@@ -60,6 +60,18 @@ Using a different MCP client? Have it run `npx -y groovehq-mcp` and set `GROOVE_
|
|
|
60
60
|
|
|
61
61
|
> **Heads up:** the package is `groovehq-mcp`, with the `hq`. `groove-mcp` doesn't work.
|
|
62
62
|
|
|
63
|
+
## Use as a library
|
|
64
|
+
|
|
65
|
+
You can run the same tools over your own transport, for example in a Cloudflare Worker. `createGrooveServer` returns a new MCP `Server` and connects nothing itself:
|
|
66
|
+
|
|
67
|
+
```ts
|
|
68
|
+
import { createGrooveServer } from 'groovehq-mcp/server';
|
|
69
|
+
|
|
70
|
+
const server = createGrooveServer({ token: 'your_token_here', readOnly: true });
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
`allowSend` and `apiUrl` are optional too. Sending stays off unless you set `allowSend: true`, and `readOnly` always wins.
|
|
74
|
+
|
|
63
75
|
## Handle with care
|
|
64
76
|
|
|
65
77
|
This server can send real email to real customers. A few things keep that honest:
|