Compare commits

..

2 Commits

Author SHA1 Message Date
app-fe b4488b224f fix(docs): remove non-existent HTTP/SSE transport and MCP_SERVER_PORT
Secret scan / secret-scan (pull_request) Successful in 25s
CI / build (pull_request) Successful in 2m41s
MCP server source confirms:
- Only StdioServerTransport exists (no HTTP/SSE server)
- No MCP_SERVER_PORT env var
- apiCall() sends no Authorization header

Removed the entire "Transport modes" section (non-existent HTTP/SSE
endpoint), MCP_SERVER_PORT row from env table and troubleshooting, and
MOLECULE_API_KEY from config examples (auth is planned, not wired yet).
Replaced with accurate "Transport" section documenting stdio-only mode.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-14 18:49:20 +00:00
app-fe 608dccc9a7 fix(docs): combine MCP HTTP/SSE transport + env vars (closes PR #42, #43)
Secret scan / secret-scan (pull_request) Successful in 10s
CI / build (pull_request) Successful in 40s
2026-05-14 16:50:25 +00:00
2 changed files with 7 additions and 24 deletions
+7
View File
@@ -42,6 +42,8 @@ For SaaS deployments, set `MOLECULE_URL` to your tenant URL:
"MOLECULE_URL": "https://your-org.moleculesai.app"
```
Auth via `MOLECULE_API_KEY` is planned for a future release.
### Verify
Once configured, your MCP client should show 87 Molecule AI tools. Test with:
@@ -152,6 +154,11 @@ The MCP server exposes tools across these categories:
| Variable | Default | Description |
|---|---|---|
| `MOLECULE_URL` | `http://localhost:8080` | Platform API URL |
| `MOLECULE_API_KEY` | — | Bearer token for platform authentication (planned) |
## Transport
The MCP server uses **stdio transport** — the client (Claude Code, Cursor, etc.) spawns the server as a child process and communicates via JSON-RPC over stdin/stdout. Configure in your AI client's `mcp.json` as shown in Quick start above.
## Troubleshooting
-24
View File
@@ -2,33 +2,9 @@ import { createMDX } from 'fumadocs-mdx/next';
const withMDX = createMDX();
// HTML pages: short edge cache + long stale-while-revalidate. Lets Vercel Edge
// serve repeat navigations from cache (~5 min fresh, 24 h stale-while-revalidate
// in the background) while keeping the browser revalidating on every nav. The
// negative lookahead leaves Next.js's own _next/static (immutable, hash-named)
// and _next/image cache headers untouched.
const HTML_CACHE_CONTROL =
'public, max-age=0, s-maxage=300, stale-while-revalidate=86400';
/** @type {import('next').NextConfig} */
const config = {
reactStrictMode: true,
async headers() {
return [
{
// Match every path except Next.js internals and API routes — those
// already have correct cache headers (immutable for hashed assets,
// app-controlled for /api).
source: '/((?!_next/static|_next/image|api/).*)',
headers: [
{
key: 'Cache-Control',
value: HTML_CACHE_CONTROL,
},
],
},
];
},
};
export default withMDX(config);