如何将 Apify Actors MCP Gateway 远程 MCP 连接到 Kiro
约 1 分钟即可把 Apify 的远程 MCP 服务端接入 Kiro。如需排查 OAuth / 401 问题,可先用 OAuth 2.1 调试器体检端点。
Streamable HTTPhttps://mcp.apify.com
Install in Cursor →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com"
}
}
}claude mcp add --transport http apify https://mcp.apify.com
Install in VS Code →
Or add to .vscode/mcp.json:
{
"servers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.apify.com - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.apify.com"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"apify": {
"serverUrl": "https://mcp.apify.com"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.apify] url = "https://mcp.apify.com"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"apify": {
"type": "streamableHttp",
"url": "https://mcp.apify.com"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"apify": {
"httpUrl": "https://mcp.apify.com"
}
}
}接入步骤
- 打开 MCP 配置 — Kiro → MCP 面板,或编辑工作区
.kiro/settings/mcp.json。 - 添加服务端 — 写入
"apify": { "url":https://mcp.apify.com}。 - 完成认证 — 首次调用时客户端会打开 Apify 的 OAuth 授权页面——点击允许后工具即可用。
- 验证 — 在 在线 Inspector 中粘贴
https://mcp.apify.com并运行 initialize + tools/list 验证连通性。
🧰 工具预览(15)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search-actors ~30 tok | 🟢 Read | Search Apify Store for Actors. | — |
| fetch-actor-details ~34 tok | 🟢 Read | Get details and input schema of an Actor. | — |
| call-actor ~30 tok | 🟠 Write | Run an Actor and get its output. | — |
| get-actor-output ~31 tok | 🟢 Read | Retrieve output of an Actor run. | — |
| add-actor ~31 tok | 🟠 Write | Add an Actor to the available toolset. | — |
| remove-actor ~31 tok | 🟠 Write | Remove an Actor from the toolset. | — |
| get-actor-run ~30 tok | 🟢 Read | Get details of an Actor run. | — |
| get-actor-log ~29 tok | 🟢 Read | Get logs of an Actor run. | — |
| scrape-single-url ~32 tok | 🟢 Read | Scrape a single URL into markdown. | — |
| fetch-apify-docs ~30 tok | 🟢 Read | Fetch Apify documentation. | — |
| search-apify-docs ~30 tok | 🟢 Read | Search Apify documentation. | — |
| get-dataset-items ~32 tok | 🟢 Read | Get items from an Apify dataset. | — |
| list-actor-runs ~29 tok | 🟢 Read | List runs of an Actor. | — |
| get-dataset ~28 tok | 🟢 Read | Get details of a dataset. | — |
| get-key-value-store ~31 tok | 🟢 Read | Get a key-value store record. | — |