docs: add MCP Connectors documentation#2568
Conversation
Introduces sources/platform/integrations/ai/mcp-connectors/ with the feature landing page and Actor-developer guide. Extends the input schema spec with the mcpConnector resourceType, adds APIFY_MCP_PROXY_URL to environment variables, and documents Connector management under console settings. Cross-links related AI pages and adds Connector capitalization to the terminology standards.
TC-MO
added
documentation
|
✅ Preview for this PR (commit |
Trim the opening sentence, convert italic-led bullet lists to flat declarative form, and inline the inbound/outbound disambiguation callout.
Distinguish APIFY_TOKEN (which the Actor uses to call the proxy) from the third-party credential (which never enters the Actor) across the landing, develop_ai_agents, and secret_input pages. Add descriptions and renamed labels to the MCP server and MCP Connectors cards on the Integrations index. Add a short "Run an Actor with a Connector" section to the landing for end-user discovery, and reframe the Authentication methods cross-link from instructional to action-oriented.
|
|
||
| MCP Connectors let Actors call third-party services - Notion, Slack, GitHub, Sentry, Supabase, and others - through [Model Context Protocol](https://modelcontextprotocol.io/docs/getting-started/intro) (MCP) on your behalf, using your credentials, without ever exposing those credentials to the Actor code. | ||
|
|
||
| You authorize a Connector once in your account settings. When you run an Actor that accepts Connectors, the input form shows a picker filtered to those compatible with the Actor's requirements. At runtime, the Apify platform injects your credentials server-side. The Actor never sees a token. |
There was a problem hiding this comment.
I'd say something like, "You authorize a Connector once in your account settings>API & Integrations (link to this - fallback to sign in)"
Dropdown selector > picker (personal preference - I don't know if "picker" is something widely understood in our industry)
For the last sentence - I'd highlight this a little more. The actor never sees a token, so your sensitive credentials are secure."
There was a problem hiding this comment.
Not sure why this one is showing as outdated when I haven't pushed anything yet on the branch 🤔
Not sure about selector vs picker. We already use picker throughout docs (both in code & in prose) while selector is not that prevalent (usually used to refer to CSS selectors.
There was a problem hiding this comment.
and on the voice I think you opened the comment yesterday and submitted it today, the wording is a bit different now so double check if still needs attention
| proxy --> external | ||
| ``` | ||
|
|
||
| 1. The Actor developer declares which Connectors the Actor accepts in its input schema. |
There was a problem hiding this comment.
This can be deterministic or open to accept any MCP Connection
There was a problem hiding this comment.
Makes sense, something like
| 1. The Actor developer declares which Connectors the Actor accepts in its input schema. | |
| 1. The Actor developer declares which Connectors the Actor accepts in its input schema (either a specific server, or any MCP-compatible Connector). |
| ``` | ||
|
|
||
| 1. The Actor developer declares which Connectors the Actor accepts in its input schema. | ||
| 1. When you run the Actor, you select an eligible Connector in the input form. If you don't have one yet, you can create and authorize a new Connector in advance under **Settings > API & Integrations**. |
There was a problem hiding this comment.
... under settings> API & Integrations, or inline within the actor input
| | _OAuth_ | The server supports OAuth and either (a) supports Dynamic Client Registration (DCR), so Apify registers an OAuth client automatically, or (b) Apify provides a managed OAuth client for that service. | | ||
| | _Own OAuth client_ | The server uses OAuth but neither DCR nor an Apify-managed client is available. You register your own OAuth app with the provider and supply the credentials to Apify. | | ||
|
|
||
| At launch, Notion and Supabase can be connected with no OAuth app setup on your side. Services such as GitHub, Slack, Google, and Microsoft require the Own OAuth Client flow - the same approach used by Claude Code, VS Code, and ChatGPT integrations. |
There was a problem hiding this comment.
Really? Is that true about Notion & Supabase? I haven't run into that.
There was a problem hiding this comment.
I was going off marketing brief, but honestly on second pass I would just drop whole line 64. It is unnecessary and it's time hedging which is not a good practice.
| - **web scraper** (never "Web Scraper") | ||
| - **proxy server** (never "Proxy Server") | ||
|
|
||
| ## MCP Connectors |
Link "Account settings" to the Console settings page, mention both specific-server and any-server input-schema modes, document the inline Connector creation path, and drop the time-hedged "Notion and Supabase at launch" paragraph. Also strip descriptions from the MCP and MCP Connectors cards on the integrations index.
|
|
||
| client -- "Bearer APIFY_TOKEN" --> proxy | ||
| proxy --> external | ||
| ``` |
There was a problem hiding this comment.
Can we add a line break between this graph & the list below? It's a nit - it just looks cleaner
3 participants
Introduces sources/platform/integrations/ai/mcp-connectors/.
Extends the input schema spec with the mcpConnector resourceType
adds APIFY_MCP_PROXY_URL to environment variables
documents Connector management under console settings
Cross-links related AI pages and adds Connector capitalization to the terminology standards.