Skip to content

[codex] Add OAuth MCP and ChatGPT app config#5

Open
SriganeshNk wants to merge 5 commits into
mainfrom
codex/add-render-oauth-mcp
Open

[codex] Add OAuth MCP and ChatGPT app config#5
SriganeshNk wants to merge 5 commits into
mainfrom
codex/add-render-oauth-mcp

Conversation

@SriganeshNk

@SriganeshNk SriganeshNk commented Jul 2, 2026

Copy link
Copy Markdown

Summary

  • Bump the plugin package to 0.2.0 and add a changelog entry.
  • Add a plugin-provided .mcp.json entry for the hosted Render MCP server.
  • Configure OAuth for Codex with the pre-registered client id codex.
  • Add .app.json for the Render ChatGPT app mapping with app id asdk_app_6a4ed9a64074819193a650ea05fd8c3b and mark it required.
  • Point plugin.json at both .mcp.json and .app.json.
  • Update README/setup docs so Codex uses plugin OAuth while manual clients continue to use API-key setup.

Impact

Codex users installing the Render plugin can get the Render MCP server from the plugin manifest and complete OAuth without manually running codex mcp add or setting RENDER_API_KEY for MCP.

The same plugin package now also carries the Render ChatGPT app mapping. It does not bundle the hosted backend; ChatGPT still connects through the hosted Render MCP service and public availability still follows the normal app review/publishing flow.

OAuth client registration

This PR declares the Codex OAuth client id in .mcp.json because Codex reads that MCP config directly. The .app.json file only maps this plugin package to the existing ChatGPT app id. The ChatGPT-side OAuth client id must be configured on the registered ChatGPT app / connector record for asdk_app_6a4ed9a64074819193a650ea05fd8c3b, not in .app.json.

Validation

  • python3 -m json.tool .mcp.json
  • python3 -m json.tool .app.json
  • python3 -m json.tool .codex-plugin/plugin.json
  • git diff --check

Note: the local plugin-creator validator available in this sandbox rejects .app.json app field required, but installed first-party app manifests in the local plugin cache use this exact required: true shape.

@SriganeshNk

Copy link
Copy Markdown
Author

I still need to verify things and we have security to go through the support because of the dynamically generated path suffix on codex.

@SriganeshNk SriganeshNk marked this pull request as ready for review July 6, 2026 22:01
@SriganeshNk

Copy link
Copy Markdown
Author

I still need to verify things and we have security to go through the support because of the dynamically generated path suffix on codex.

this is done!

SriganeshNk and others added 2 commits July 6, 2026 15:10
The skills/ directory is synced from render-oss/skills, so per-plugin edits
there get overwritten on the next sync. Keep only the plugin's own .mcp.json,
manifest, and README; the OAuth wording lives in the shared skills.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codex derives the OAuth resource from the server URL; also setting
oauth_resource makes it send the resource parameter twice, which the
server rejects with invalid_target ("only a single resource parameter
is supported").

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@R4ph-t R4ph-t left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @sriganesh. just a note on the versioning, non blocking

Comment thread .codex-plugin/plugin.json Outdated
@SriganeshNk SriganeshNk changed the title [codex] Add OAuth MCP config for Codex [codex] Add OAuth MCP and ChatGPT app config Jul 10, 2026
@SriganeshNk SriganeshNk marked this pull request as draft July 10, 2026 21:46
@SriganeshNk SriganeshNk marked this pull request as ready for review July 10, 2026 22:09
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.

2 participants