8da0c47955
Plugin v0.2 polls /activity?since_id=<cursor>. Older platforms (pre molecule-core#2354) silently ignore the param and return whatever the default time window covers — every poll then re-delivers the same activities to Claude as fresh turns. That's a worse failure mode than any v0.1 bug. Add a startup probe: send since_id=00000000-…-000000000000 (the all-zero UUID, which gen_random_uuid() can never produce per RFC 4122 §4.4 so a valid 410 is unambiguous). #2354+ answers 410 Gone for any unknown cursor; pre-#2354 answers 200 OK. On 200 the plugin exits with code 2 and a clear "upgrade your platform or downgrade the plugin" message. 401/403/404/5xx are inconclusive (orthogonal to cursor support) — log a warning, let the normal poll loop surface the real failure. Bumps package.json + the MCP server-name version string to 0.2.1 (the 0.1.0 in the Server constructor was already stale, fixed at the same time). README's compat section documents the probe + exit code so users debugging an immediate exit-code-2 know what's going on. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 lines
396 B
JSON
15 lines
396 B
JSON
{
|
|
"name": "molecule-mcp-claude-channel",
|
|
"version": "0.2.1",
|
|
"description": "Molecule AI channel for Claude Code — bridges A2A traffic into a Claude Code session via MCP",
|
|
"license": "Apache-2.0",
|
|
"type": "module",
|
|
"bin": "./server.ts",
|
|
"scripts": {
|
|
"start": "bun install --no-summary && bun server.ts"
|
|
},
|
|
"dependencies": {
|
|
"@modelcontextprotocol/sdk": "^1.0.0"
|
|
}
|
|
}
|