docs: edit build with AI page to reflect changes in MCP

[patrikbraborec]

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.

• Docs (build-with-ai):
  • Add setup instructions for Apify MCP Server in Claude, Cursor (with mcp.json snippet), and VS Code using https://mcp.apify.com/?tools=docs.
  • Streamline MCP configuration note and improve guidance for providing context via Copy for LLM and /llms.txt.
  • Remove unused InstallMCPButton import.
• Cleanup:
  • Delete src/components/InstallMCPButton.jsx and src/components/InstallMCPButton.module.css.

^{Written by Cursor Bugbot for commit 5e93989. Configure here.}

[apify-service-account]

Preview for this PR was built for commit 5e93989 and is ready at https://pr-2119.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 5867d5f and is ready at https://pr-2119.preview.docs.apify.com!

[TC-MO]

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

:::info Use Apify MCP server configuration

We have prepared the [Apify MCP server configuration](https://mcp.apify.com/), which you can configure for your needs.

:::

it would rather say soemthing like

:::note No authentication required

The documentation tools in the Apify MCP server do not require an API token. You can use them freely without logging in.

:::

[apify-service-account]

Preview for this PR was built for commit e37f33aa and is ready at https://pr-2119.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit e37f33aa and is ready at https://pr-2119.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 12fb6c79 and is ready at https://pr-2119.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit f931e59 and is ready at https://pr-2119.preview.docs.apify.com!

[patrikbraborec]

Hi @TC-MO! Thanks for the changes, and review - accepted.

Regarding:

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?

I think that the current version is better. Promoting MCP documentation tools without auth is like promoting documentation without auth. If you check other dev tools, most of them have MCP documentation tools without auth, and thus it does not make sense to promote it.