Automate browser based workflows with AI
Python aiapiautomationbrowserbrowser-automationcomputergptllmplaywrightpowerautomatepuppeteerpythonrpaseleniumvisionworkflow
fix(mcp): accept trailing-slash resource in MCP OAuth authorize (unblocks Codex CLI) (#6944)
Marc Kelechavaa2dda9c8b5df
diff --git a/docs/snippets/mcp-content.mdx b/docs/snippets/mcp-content.mdxindex 74842cab8..debd52f1b 100644--- a/docs/snippets/mcp-content.mdx+++ b/docs/snippets/mcp-content.mdx@@ -64,6 +64,16 @@ codex mcp get skyvernIf you previously configured Skyvern with an `x-api-key` header, run `codex mcp remove skyvern` first so Codex does not skip the OAuth handshake. You do not need to run `codex mcp login skyvern` after `add` — the OAuth flow runs inline. Use `codex mcp login skyvern` only to re-authenticate after a token expires or to request custom `--scopes`.+<Note>+If `codex mcp add` fails with `resource is not allowed for this authorization server`, your Codex version derived a trailing-slash `resource` from the URL. Pass the slashless resource explicitly:++```bash+codex mcp add skyvern --url https://api.skyvern.com/mcp/ --oauth-resource https://api.skyvern.com/mcp+```++Skyvern Cloud accepts both forms, so the flag is only needed on older self-hosted deployments.+</Note>+</Tab><Tab title="Cursor">