Repository navigation
docs: Add Claude.ai integration page - #3162
marcel-rbro wants to merge 10 commits into
Conversation
Add a setup guide for claude.ai that installs the Apify plugin from the connector directory and connects its Apify MCP connector, with a custom connector alternative for limiting tools. Point the Claude Desktop remote server section to it instead of repeating the steps, and link it from the Claude overview, MCP server, and agent onboarding pages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
✅ Preview for this PR (commit |
Rename the Claude Desktop methods to "Apify plugin or custom connector" and "Desktop extension" so they match the Claude.ai page, and shorten the remote setup section to a link. On the Claude.ai page, fold the dynamic registration warning into the sign-in step, add a tool permissions check to troubleshooting, and update the screenshot placeholders. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Resolve agent-onboarding.md deletion by moving the claude.ai link change to agents/quickstart.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Add screenshots for the plugin in Discover, the plugin's Connectors tab, and the Apify permission page. Merge the connector dialog steps, make the account choice a regular step, and split the permission checks from the warning. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
TC-MO
left a comment
There was a problem hiding this comment.
Moving the hosted setup to one page makes sense, and the page follows the plugin template well. The two main points are the Team/Enterprise sentence that got lost and the leftover "connector" wording on the Desktop page. The rest are small.
I couldn't check the claude.ai UI paths. I assume you tested them live.
|
|
||
| <ApifyPluginSkillPrompts /> | ||
|
|
||
| ## Connect without the plugin |
There was a problem hiding this comment.
Nit, take it or leave it: on the sibling plugin pages (Cursor, Codex), setup comes first, then usage, then troubleshooting. Here an alternative setup path sits after Bundled skills. You could move it above Run your first prompt, but it's also fine where it is as the advanced path.
There was a problem hiding this comment.
I'd keep it here, it's an advanced flow. If I were to rewrite the other pages, I'd move it as well.
Restore the Team/Enterprise owner note, drop the redundant Connectors tab screenshot, add a Troubleshooting intro, and use "extension" instead of "connector" for the Claude Desktop extension. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closes #3161
Adds a Claude.ai integration page at
/integrations/claude-ai. The claude.ai setup steps were previously buried in the Claude Desktop page.Why the setup moved to the claude.ai page
I decided to move the hosted setup (the Apify plugin and the custom connector) from the Claude Desktop page to the new claude.ai page. Connectors belong to the Claude account, so a connector added in claude.ai also works in Claude Desktop. One set of steps in one place means the two pages can't drift apart. The Desktop page now covers only what is specific to Desktop, the Desktop extension, and links to the claude.ai page for the rest.
Changes
agents/claude/claude-ai.md. It follows the plugin-page template (Cursor, Codex, Grok Bot) and covers:apifyconnector through OAuth.The example prompt uses the
promptcode block. The skill prompts keep the shared snippet, so they still match the other agent pages.Related: #2873
🤖 Generated with Claude Code