Agent context single source#6747
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0a93813. Configure here.
| "id": "codex", | ||
| "repository": "mintlify/codex-plugin", | ||
| "mcpConfigFile": ".mcp.json", | ||
| "mcpConfigKey": "mcp_servers" |
There was a problem hiding this comment.
Wrong Codex MCP config key
High Severity
Codex target packaging writes MCP servers under mcp_servers, but Codex plugin .mcp.json loading expects mcpServers (or a top-level server map). Generated Codex MCP config is likely ignored, so Mintlify Search/Admin would not register from the synced plugin.
Reviewed by Cursor Bugbot for commit 0a93813. Configure here.
There was a problem hiding this comment.
Verified against the live codex-plugin repo: its committed .mcp.json already uses mcp_servers (snake_case), matching this target config. Codex's own config format uses snake_case — see docs/ai/model-context-protocol.mdx and docs/guides/codex.mdx, which document Codex's TOML config as [mcp_servers.<name>], distinct from Claude/Cursor's mcpServers.
The "mcpServers": "./.mcp.json" field in .codex-plugin/plugin.json is unrelated — that's the plugin manifest's pointer key (which file to load), not the schema inside that file. No change needed here.
2 participants
Documentation changes
Sets up GitHub action to single source all our agent plugins (Claude, Cursor, Codex) from the docs repo.
For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience
Note
Medium Risk
New cross-repo automation depends on GitHub App secrets and writes to three external plugin repositories via force-pushed branches; failures or misconfiguration could block or mis-sync agent context, but changes do not touch production docs or user-facing site content directly.
Overview
Introduces
agent-context/in the docs repo as the canonical source for the shared Mintlify agent skill and MCP server definitions, instead of maintaining separate copies in each plugin repo.Build and sync: Node scripts (
build.mjs,sync-target.mjs,lib.mjs) render per-target artifacts (Codex, Cursor, Claude) with only packaging differences intargets/*.json(MCP config filename and JSON key). Sync replacesskills/mintlify/, the client MCP file, and.mintlify-agent-context.jsonprovenance; plugin-owned files stay untouched. Tests andnpm run checkenforce identical shared reference markdown across targets and block retired CLI strings in the skill.Automation:
agent-context-ci.ymlruns test/check/build on PRs and main whenagent-context/**changes.sync-agent-context.ymlvalidates, then matrix-syncs to the three plugin repos via a GitHub App, pushingautomation/sync-agent-contextand opening or updating sync PRs (never direct pushes tomain).Docs site: Root
.mintignoreexcludesagent-context/from published Mintlify docs.Reviewed by Cursor Bugbot for commit 0a93813. Bugbot is set up for automated code reviews on this repo. Configure here.