Compare commits

...

2 Commits

Author SHA1 Message Date
hongming-pc2 e267875fb3 Merge PR #18 via Gitea merge queue
CI / test (push) Successful in 36s
Serialized merge by gitea-merge-queue after current-main, SOP, and required CI checks were green.
2026-05-17 19:13:13 +00:00
sdk-dev 68e0505d9f docs(mcp): fix stale SDK reference in Platform Integration section
[Do] Manual gate post
sop-checklist / all-items-acked Manual gate post
CI / test (pull_request) Successful in 19s
PR #17 updated known-issues.md but dropped the CLAUDE.md fix.
The Platform Integration section incorrectly claimed the server uses
the Python SDK (molecule-sdk-python). The MCP server has its own
TypeScript client in src/api.ts — the Python SDK is for remote agents.

Also fixed "reads data via the platform SDK" → "reads data via the
platform REST API" in the Postgres section.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-17 00:14:04 +00:00
+5 -2
View File
@@ -96,7 +96,10 @@ The workflow:
### APIs Connected
The server connects to the Molecule AI platform REST API. See the platform SDK (`../molecule-sdk-python`) for the underlying API client used.
The server connects to the Molecule AI platform REST API via its own TypeScript
client (`src/api.ts`). It does not use the Python SDK (`molecule-sdk-python`) —
the Python SDK is for remote agents that run outside the platform; this server
runs as an MCP bridge *on* the operator side.
### Environment Variables
@@ -110,7 +113,7 @@ For local development, copy `.env.example` → `.env` and fill in values.
### Postgres
Platform data lives in Postgres (source of truth). The server reads data via the platform SDK — it does not connect to Postgres directly.
Platform data lives in Postgres (source of truth). The server reads data via the platform REST API — it does not connect to Postgres directly.
## TypeScript Conventions