Skip to content

Fix MCP vector attachments and TSV input; align public documentation - #3

Merged
jwildenhain merged 1 commit into
masterfrom
codex/mcp-docs-parity
Sep 18, 2026
Merged

jwildenhain merged 1 commit into
masterfrom
codex/mcp-docs-parity

Conversation

@jwildenhain

Copy link
Copy Markdown
Owner

The public MCP endpoint generated SVG/PDF files but serialized their payloads as JSON text, and advertised TSV input was passed to a comma-only R parser. Return typed embedded resources for SVG/PDF and select the delimiter in the shared plotting worker. PNG remains an MCP image.

Clarify the public output_format interface versus local stdio output_path in the FAQ, MCP tab, README, and illustrated guide, including the options that are only exposed locally. Expand HTTP integration checks to both engines, CSV/TSV, and all three formats, verifying attachment structure, MIME types, decoded file contents, and tool discovery.

Validation: the 12-case HTTP matrix passed in an isolated server using the installed production dependencies. Worker regressions cover tool discovery, Tukey whiskers, and six direct render formats. Local R/Python parsing and whitespace checks passed. Container CI must pass before the authorized production rollout; the rollout backs up changed files and provides rollback commands.

@jwildenhain
jwildenhain merged commit 24e14e6 into master Sep 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant