fix(openapi): add MCP to RunOrigin enum#2752
Merged
Merged
Conversation
Contributor
|
🗑️ Preview for this PR was deleted. |
Contributor
|
Important Action required — @vdusek please coordinate this docs PR with the Python API client PR linked below. Because this PR modifies the OpenAPI specification, the generated models in A companion PR has been opened in
|
vdusek
pushed a commit
to apify/apify-client-python
that referenced
this pull request
Jul 8, 2026
- Updates the auto-generated Pydantic models and TypedDicts based on the proposed OpenAPI specification changes. - Based on apify-docs PR [#2752](apify/apify-docs#2752).
Pijukatel
approved these changes
Jul 8, 2026
vdusek
added a commit
to apify/apify-shared-python
that referenced
this pull request
Jul 8, 2026
Add the two `MetaOrigin` values the platform already emits but the Python enum was missing, bringing it to parity with `apify-shared-js`: - `MCP` — runs started through the Apify client triggered from the Apify MCP server. - `CI` — runs started from a CI/CD pipeline (e.g. GitHub Actions). Without `MCP`, any Actor invoked via the Apify MCP server crashes at startup: the released SDK line (`apify` 3.4.x) validates `run.meta.origin` against `apify_shared.consts.MetaOrigin`, and an unknown value raises a `pydantic.ValidationError` before user code runs. Related: apify/apify-sdk-python#1032. The API OpenAPI spec is fixed in parallel (apify/apify-docs#2752), which covers the SDK master line that reads the enum from `apify-client` v3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add
MCPto theRunOriginenum in the OpenAPI spec.The Apify MCP server starts Actor runs with
meta.origin: "MCP", but the spec'sRunOriginenum doesn't list that value. As a result, generated typed clients reject any such run during validation.apify-shared-jsalready includesMCP, so the spec is the last place still missing it.Why
This is the root cause of apify/apify-sdk-python#1032. Every Python Actor invoked via the Apify MCP server crashes at startup, before user code runs, because the generated
apify-clientmodel validatesmeta.originagainst a strict enum that has noMCPmember.Fixing the enum here propagates down the chain:
apify-client-pythonregenerates its models from this spec (docs.apify.com/api/openapi.json), soRunOriginpicks upMCP.Follows the same pattern as #2559, which added
CIto the same enum.🤖 Generated with Claude Code