docs: align agent onboarding and MCP server pages with the live MCP server and skills

sources/_partials/_apify-plugin-skill-prompts.mdx

@@ -6,6 +6,6 @@ To run `apify-actor-development`:
 
 > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL.
 
-To run `apify-sdk-integration`:
+To run `apify-integration-development`:
 
 > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON.

sources/_partials/_apify-plugin-skills.mdx

@@ -4,4 +4,4 @@
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product - workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |

sources/platform/get-started/agent-onboarding.md

@@ -90,9 +90,12 @@ The pattern is the same across every integration method: pick an Actor, send inp
 
 When an agent calls Actors automatically, set run limits to prevent surprise bills. Pass these as query parameters on the [run Actor endpoint](/api/v2/actors-runs-post):
 
-- `memory` (MB) - power of 2, minimum 128. Lower memory means lower cost per second.
+- `maxTotalChargeUsd` - cap the total amount charged for the run. Works for all pricing models.
+- `maxItems` - cap the number of billed dataset items. Pay-per-result Actors only.
 - `timeout` (seconds) - cap how long a single run can last.
-- `maxTotalChargeUsd` - cap total run cost for pay-per-event Actors.
+- `memory` (MB) - power of 2, minimum 128. Lower memory means lower cost per second.
+
+Over MCP, pass the same caps in the `callOptions` argument of `call-actor`. Never put them in the Actor input, where they are ignored or rejected.
 
 See [Usage and resources](/actors/running/usage-and-resources) and [Billing](/account/billing) for details.
 
@@ -117,9 +120,7 @@ The MCP server's `search-actors`, `fetch-actor-details`, and docs tools work wit
 
 :::
 
-#### Remote (recommended)
-
-Works with Claude Code, Cursor, VS Code, GitHub Copilot, and other remote-capable clients.
+Works with Claude Code, Claude Desktop, Cursor, VS Code, GitHub Copilot, and other remote-capable clients.
 
 1. Add the following to your MCP client's configuration:
 
@@ -135,27 +136,7 @@ Works with Claude Code, Cursor, VS Code, GitHub Copilot, and other remote-capabl
 
 1. Restart your client and sign in when prompted. OAuth handles authentication automatically.
 
-#### Local/stdio
-
-For clients that only support local MCP servers, for example Claude Desktop.
-
-1. Add the following to your MCP client's configuration:
-
-    ```json
-    {
-      "mcpServers": {
-        "apify": {
-          "command": "npx",
-          "args": ["-y", "@apify/actors-mcp-server"],
-          "env": { "APIFY_TOKEN": "YOUR_TOKEN" }
-        }
-      }
-    }
-    ```
-
-1. Replace `YOUR_TOKEN` with your API token and restart the client.
-
-For client-specific setup instructions, use the [MCP Configurator](https://mcp.apify.com) which generates ready-to-paste configs. For details, see the [MCP server documentation](/integrations/mcp).
+For client-specific steps, use the [MCP Configurator](https://mcp.apify.com), which generates ready-to-paste configs. For a client that supports only local MCP servers, tool selection, and Bearer token authentication, see the [MCP server documentation](/integrations/mcp).
 
 ### API client
 
@@ -283,7 +264,7 @@ npx skills add apify/agent-skills
 | `apify-actor-development` | Guided workflow for building and deploying custom Actors |
 | `apify-actorization` | Converts an existing project into an Apify Actor |
 | `apify-generate-output-schema` | Auto-generates output schemas from Actor source code |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code |
 
 For the full list and details, see the [skills registry](https://skills.sh/apify/agent-skills).
 

sources/platform/integrations/ai/claude/claude-code-cli.md

@@ -100,7 +100,7 @@ The agent searches Apify Store, fetches the top Actor's details through `plugin:
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |
 
 Example prompts that route to specific skills:
 

sources/platform/integrations/ai/cursor.md

@@ -88,7 +88,7 @@ The agent searches Apify Store, fetches the top Actor's details through the Apif
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |
 
 Example prompts that route to specific skills:
 

sources/platform/integrations/ai/kimi-code-cli.md

@@ -92,7 +92,7 @@ The router searches Apify Store, fetches the top Actor's details through the Api
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |
 
 Example prompts that route to specific skills:
 

sources/platform/integrations/ai/manus.md

@@ -109,7 +109,7 @@ Available skills include:
 | `apify-actor-development` | Full Actor lifecycle: template selection, development, testing, and deployment |
 | `apify-actorization` | Converts existing projects into Apify Actors |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas from Actor source code |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code |
 
 ### Import a skill from GitHub
 

sources/platform/integrations/ai/mcp.md

@@ -48,7 +48,7 @@ The MCP server intentionally excludes two categories of Actors from search and e
 Before connecting your AI to Apify, you'll need three things:
 
 - _An Apify account_ - Sign up for an Apify account, if you don't have one.
-- _Apify API token_ - Get your API token from the **API & Integrations** section in [Apify Console](https://console.apify.com/settings/integrations). This token authorizes the MCP server to run Actors on your behalf. Make sure to keep it secure.
+- _Apify API token_ - Only needed for the [local stdio server](#local-stdio) or the Bearer token option. The recommended remote connection signs you in with OAuth instead. Get your token from the **API & Integrations** section in [Apify Console](https://console.apify.com/settings/integrations) and keep it secure.
 - _MCP client_ - An AI agent or client that supports Model Context Protocol (MCP) This could be Anthropic's Claude for Desktop, a VS Code extension with MCP support, or any application that implements the MCP specification. The [official MCP documentation](https://modelcontextprotocol.io/clients) maintains a list of compatible clients.
 
 ## Connect and authorize

sources/platform/integrations/ai/openai/codex-app.md

@@ -89,7 +89,7 @@ Codex searches Apify Store, fetches the top Actor's details through the `apify`
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |
 
 Example prompts that route to specific skills:
 

sources/platform/integrations/ai/openai/codex-cli.md

@@ -87,7 +87,7 @@ It then summarizes the Actor's inputs, pricing, and output - all without running
 | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. |
 | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
 | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. |
-| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. |
+| `apify-integration-development` | Builds an official Apify integration for another product: workflow-automation apps, agent plugins, AI framework packages, or `apify-client` application code. |
 
 Example prompts that route to specific skills: