Gantt charts in Any other client
Standard JSON block, or the mcp-remote stdio bridge
Add the server once and Any other client can schedule a whole project for you — dependencies, working calendars, resource levelling and critical path — then hand back a shareable chart plus PNG, SVG and CSV exports.
Set it up in 5 steps
Try the native HTTP block first — add this to the client's mcpServers config file. Key names differ per client: Claude Code requires the `type` field (an entry with `url` but no `type` is a hard configuration error), VS Code uses the same object under a `servers` key in `.vscode/mcp.json`, and Cursor uses `mcpServers` in `.cursor/mcp.json` with a bare `url` and no `type`.
.mcp.json / mcpServers config (Claude Code's standardized format) { "mcpServers": { "gantt": { "type": "http", "url": "https://gantt.nare.li/api/mcp" } } }If the client is stdio-only, or speaks HTTP but can't run the MCP OAuth flow, bridge it with mcp-remote and force HTTP transport. `--transport http-only` is required here: the default `http-first` strategy falls back to SSE on a 404, and this server has no SSE endpoint.
stdio-only clients: mcp-remote proxy { "mcpServers": { "gantt": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gantt.nare.li/api/mcp", "--transport", "http-only" ] } } }Restart the client and finish the browser consent screen that opens on first connect. mcp-remote listens on port 3334 for the OAuth redirect by default (pass a port number as an extra argument after the URL to change it; if the port is busy it picks a random open one).
If auth loops or tokens go stale, clear the bridge's credential cache and restart the client. Add `--debug` to write a verbose auth log to the same directory.
bash rm -rf ~/.mcp-authCalling the Messages API directly? Attach it as an MCP connector — but note this path does NOT run OAuth for you: you must obtain and refresh the access token yourself.
Anthropic Messages API (beta: mcp-client-2025-11-20) curl https://api.anthropic.com/v1/messages \ -H "Content-Type: application/json" \ -H "X-API-Key: $ANTHROPIC_API_KEY" \ -H "anthropic-version: 2023-06-01" \ -H "anthropic-beta: mcp-client-2025-11-20" \ -d '{ "model": "claude-opus-5", "max_tokens": 1000, "messages": [{"role": "user", "content": "What tools do you have available?"}], "mcp_servers": [ { "type": "url", "url": "https://gantt.nare.li/api/mcp", "name": "gantt", "authorization_token": "YOUR_ACCESS_TOKEN" } ], "tools": [ { "type": "mcp_toolset", "mcp_server_name": "gantt" } ] }'
mcp-remote must be 0.1.16 or newer (CVE-2025-6514) and needs Node 18+.
Once it is connected
Ask Any other client: “Plan a 6-week website rebuild for a team of four and give me the chart.”