Skip to content

docs: Add custom connector setup steps for Claude - #2950

Open
marcel-rbro wants to merge 9 commits into
masterfrom
docs/claude-custom-connector
Open

marcel-rbro wants to merge 9 commits into
masterfrom
docs/claude-custom-connector

Conversation

@marcel-rbro

Copy link
Copy Markdown
Contributor

What changed

The Claude Desktop integration page covered the remote server in a single sentence ("add a custom connector and use https://mcp.apify.com as the server URL") that linked out to Anthropic's support article for the actual steps. This replaces it with the concrete step-by-step flow, which is identical in Claude Desktop and in Claude on the web:

  1. Open Settings > Connectors and select Add custom connector.
  2. Name the connector.
  3. Enter https://mcp.apify.com as the remote MCP server URL.
  4. Select Continue.
  5. Keep the recommended settings and select Add.

Also adds a tip pointing to the Apify MCP server configurator for users who want to expose specific Actors or tools instead of the default tool set.

Why

Requested so the setup instructions live on the existing integration page rather than on a new separate page.

Refs #2873.

Replace the single-sentence remote server instruction on the Claude
Desktop integration page with the step-by-step custom connector flow,
and point users to the MCP server configurator for custom tool sets.

Refs #2873
@github-actions github-actions Bot added the t-docs Issues owned by technical writing team. label Sep 4, 2026
@apify-service-account

apify-service-account commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit 9413635) is ready at https://pr-2950.preview.docs.apify.com (see action run).

Spell out the navigation path to the connector settings in Claude
Desktop and in Claude on the web, split the dialog step out, and move
the tool-selection tip above the procedure so it is read before the
server URL is entered.
Anthropic's own docs call the web surface claude.ai, not "Claude on the
web", and the connector settings path differs by plan (Customize >
Connectors on Pro and Max, Organization settings > Connectors on Team
and Enterprise). Drop the unverified dialog field labels.
Keep the connector location generic so the steps survive UI changes.
Restore the verified field labels (Name, Remote MCP server URL), route
the dialog through the Add menu on the Connectors page, and note that
Claude probes the server and pre-fills the authentication and OAuth
settings it detects.
Name the roles Anthropic names (Owner or Primary Owner) and link to the
support article that states the requirement.
@marcel-rbro
marcel-rbro marked this pull request as ready for review September 4, 2026 12:44
Lift the Team and Enterprise precondition ahead of the procedure so it
is read before step 1, name the alternative URL where it is entered
rather than only in the tip below, scope the dialog deep link to
claude.ai, and trim the repetition out of the tip.
@marcel-rbro
marcel-rbro requested review from TC-MO and a lite review from Copilot and removed request for Copilot September 17, 2026 14:50

@TC-MO TC-MO left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve with medium & minor nits


1. In Claude, open **Settings**, then select **Connectors**.
1. Select **Add**, then select **Add custom connector**. In claude.ai, you can also [open the **Add custom connector** dialog](https://claude.ai/new?modal=add-custom-connector#settings/customize-connectors) directly.
1. Fill in the dialog:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We mention custom URL but don't explain it until tip admonition. Ideally it would work without that.

I can see two outcomes:

  1. Remove mention of custom URL from the step and let admonition explain the possibility.
  2. Link the configurator in the steps and slim the admonition to just point to the tool selection.


The MCP server shows as connected but Apify tools don't appear in the tools list, or Claude doesn't recognize any Apify tools in conversation.

- _Check tool permissions._ Individual connector tools can be blocked in your [connector settings](https://support.anthropic.com/en/articles/11175166-how-to-manage-and-remove-integrations-in-claude). Verify that Apify tools are set to **Always allow** or **Ask first**, not blocked.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: This is link to the same article as on LOC 36, but different, could we align?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants