Skip to content

Commit f8d417e

Browse files
committed
slight adjustments to H2 paragraphs
1 parent 68d98c3 commit f8d417e

File tree

1 file changed

+7
-9
lines changed
  • sources/platform/integrations/ai

1 file changed

+7
-9
lines changed

sources/platform/integrations/ai/mcp.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Before connecting your AI to Apify, you'll need three things:
2525

2626
## Quick start
2727

28-
To get started with the Apify MCP server you have two options.
28+
You can connect to the Apify MCP server in two ways: use our hosted service for a quick and easy setup, or run the server locally for development and testing.
2929

3030
### Streamable HTTP with OAuth (recommended)
3131

@@ -154,23 +154,21 @@ This dynamic discovery means your AI can adapt to new tasks without manual confi
154154

155155
### Production best practices
156156

157-
For production deployments, explicitly specify which tools to load rather than relying on defaults. This ensures consistent behavior across updates:
157+
- For production deployments, explicitly specify which tools to load rather than relying on defaults. This ensures consistent behavior across updates:
158158

159-
`npx @apify/actors-mcp-server --tools apify/web-scraper,apify/google-search-scraper`
159+
`npx @apify/actors-mcp-server --tools apify/web-scraper,apify/google-search-scraper`
160160

161-
Always use the latest version of the server by appending `@latest` to your npm commands. Monitor your API usage through Apify Console to stay within your plan limits.
161+
- Always use the latest version of the server by appending `@latest` to your npm commands.
162+
- Monitor your API usage through Apify Console to stay within your plan limits.
163+
- For optimal performance, batch related operations when possible and use Actor webhooks for long-running tasks instead of polling for results.
162164

163-
### Rate limits and performance
165+
## Rate limits and performance
164166

165167
The Apify MCP server allows up to _30_ requests per second per user. This limit applies to all operations including Actor runs, storage access, and
166168
documentation queries. If you exceed this limit, you'll receive a `429` response and should implement appropriate retry logic.
167169

168-
For optimal performance, batch related operations when possible and use Actor webhooks for long-running tasks instead of polling for results.
169-
170170
## Troubleshooting
171171

172-
This section covers common issues you might encounter while using the Apify MCP server.
173-
174172
### Authentication errors
175173

176174
- _Check your API token_: Verify that your Apify API token is correct. You can find it in the **Integrations** section of the [Apify Console](https://console.apify.com/account#/integrations). Without a valid token, the server cannot start Actor runs.

0 commit comments

Comments
 (0)