-
Notifications
You must be signed in to change notification settings - Fork 143
docs: edit build with AI page to reflect changes in MCP #2119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
| import { AGENTS_PROMPT } from "@site/src/utils/agents-prompt"; | ||
| import PromptButton from "@site/src/components/PromptButton"; | ||
| import InstallMCPButton from "@site/src/components/InstallMCPButton"; | ||
| import copyForAI from "./images/copy-for-ai.png"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| import copyForAI from "./images/copy-for-ai.png"; | |
| import copyForAI from "./images/copy-for-ai.png"; | |
| import Tabs from '@theme/Tabs'; | |
| import TabItem from '@theme/TabItem'; |
| ### Claude | ||
|
|
||
| 1. Go to _Settings_ > _Connectors_ in Claude. | ||
| 2. Click _Add custom connector_. | ||
| 3. Set the name to `Apify` and the URL to `https://mcp.apify.com/?tools=docs`. | ||
| 4. When chatting, click the _+_ button and select the _Apify_ connector to add documentation context. | ||
|
|
||
| ### Cursor | ||
|
|
||
| 1. Open the command palette with `Cmd+Shift+P` (or `Ctrl+Shift+P` on Windows). | ||
| 2. Search for and select _Open MCP settings_. | ||
| 3. Add the following configuration to `mcp.json`: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "apify": { | ||
| "url": "https://mcp.apify.com/?tools=docs" | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### VS Code | ||
|
|
||
| 1. Install an MCP-compatible extension. | ||
| 2. Add the Apify server URL: `https://mcp.apify.com/?tools=docs` | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few questions here:
- when you are talking about Claude do you mean web app or Claude desktop?
- I've broken up VSC to have both github copilot vsrsion and MCP-comptabile extension
| ### Claude | |
| 1. Go to _Settings_ > _Connectors_ in Claude. | |
| 2. Click _Add custom connector_. | |
| 3. Set the name to `Apify` and the URL to `https://mcp.apify.com/?tools=docs`. | |
| 4. When chatting, click the _+_ button and select the _Apify_ connector to add documentation context. | |
| ### Cursor | |
| 1. Open the command palette with `Cmd+Shift+P` (or `Ctrl+Shift+P` on Windows). | |
| 2. Search for and select _Open MCP settings_. | |
| 3. Add the following configuration to `mcp.json`: | |
| ```json | |
| { | |
| "mcpServers": { | |
| "apify": { | |
| "url": "https://mcp.apify.com/?tools=docs" | |
| } | |
| } | |
| } | |
| ``` | |
| ### VS Code | |
| 1. Install an MCP-compatible extension. | |
| 2. Add the Apify server URL: `https://mcp.apify.com/?tools=docs` | |
| <Tabs> | |
| <TabItem value="cursor" label="Cursor"> | |
| To add Apify MCP server to Cursor manually: | |
| 1. Create or open the `.cursor/mcp.json` file. | |
| 1. Add the following to the configuration file: | |
| ```json | |
| { | |
| "mcpServers": { | |
| "apify": { | |
| "url": "https://mcp.apify.com/?tools=docs" | |
| } | |
| } | |
| } | |
| ``` | |
| </TabItem> | |
| <TabItem value="vscode" label="VS Code"> | |
| VS Code supports MCP through MCP-compatible extensions like _GitHub Copilot_, _Cline_, or _Roo Code_. | |
| 1. Install an MCP-compatible extension (e.g., GitHub Copilot, Cline). | |
| 1. Locate the extension's MCP settings or configuration file (often `mcp.json`). | |
| - For _GitHub Copilot_: Run the **MCP: Open User Configuration** command. | |
| - For _MCP-compatible extension_: Go to the MCP Servers tab in the extension interface. | |
| 1. Add the Apify server configuration: | |
| ```json | |
| { | |
| "mcpServers": { | |
| "apify": { | |
| "url": "https://mcp.apify.com/?tools=docs" | |
| } | |
| } | |
| } | |
| ``` | |
| </TabItem> | |
| <TabItem value="claude" label="Claude"> | |
| 1. Go to **Settings** > **Connectors** in Claude. | |
| 1. Click **Add custom connector**. | |
| 1. Set the name to `Apify` and the URL to `https://mcp.apify.com/?tools=docs`. | |
| 1. When chatting, select the **+** button and choose the **Apify** connector to add documentation context. | |
| </TabItem> | |
| </Tabs> |
|
I'm also debating whether we should remake the admoniton that is on L60 to be specific about documentation tool not needing auth, instead of about UI configurator. Seems to me we want ro push doc tool here more. Thoughts? it would be; instead of it would rather say soemthing like |
The Apify MCP Server will not require auth for documentation tools (apify/apify-mcp-server#341). This PR makes changes regarding to it - mainly improvements to the Build with AI page.
I also checked the Apify MCP Server documentation page, but I do not see a good place, where we should mention that documentation tools do not need auth (it would probably add confusion).
I plan to update mcp.apify.com page, and also will discuss whatever we will add the following option to AI Dropdown: #2079.
Note
Updates the Build with AI guide with MCP server setup for Claude, Cursor, and VS Code, and removes the unused InstallMCPButton component and styles.
Claude,Cursor(withmcp.jsonsnippet), andVS Codeusinghttps://mcp.apify.com/?tools=docs./llms.txt.InstallMCPButtonimport.src/components/InstallMCPButton.jsxandsrc/components/InstallMCPButton.module.css.Written by Cursor Bugbot for commit 5e93989. Configure here.