The GTM MCP Directory
Directory / MCP Layer / Claude / Anthropic MCP Connector Directory

Claude / Anthropic MCP Connector Directory

MCP not applicable Free to start MCP Layer RESEARCHED Checked 2026-08-24
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: claude.com/partners/mcp · entry id 07-claude-anthropic-mcp-connector-directory · source 07-mcp-infrastructure.md line 204

What it does
Anthropic's own curated, in-product directory of MCP connectors that Claude users can browse and one-click-connect to, filterable by use case (sales, marketing, data, etc.) and by capability (read / read-write / interactive).
AI features, separated from automation with an AI label on it
none in the directory itself - it is a discovery/connection UI inside Claude, not an AI feature; the AI is Claude, using whichever connector you authorize.
RevOps role
The most mainstream on-ramp for a non-engineer GTM user to connect Claude directly to their stack; listed connectors during this check included CRM/sales tools (ActiveCampaign, Apollo.io, Affinity), analytics, and productivity apps, filterable by "sales" use case.
MCP server
Status bucket
MCP not applicable
Auth
Per-connector OAuth - Claude shows the requested scopes at connect time and lets the user limit or deny them; connectors are built and maintained by third-party developers against the MCP spec, with Anthropic publishing separate MCP Directory Terms and Policies for listed providers.
Parsed URLs
1 found in the mcp_url field

An MCP server is not a meaningful question for this entry. The status was established on 2026-08-24.

mcp_status, verbatim from the file:

n/a (this is Anthropic's own directory, not a single vendor's MCP)

mcp_url, verbatim from the file:

https://claude.com/connectors (redirect correction 2026-08-28: the address previously recorded here, www.claude.com/partners/mcp, 301s to claude.com/partners/mcp, which 301s again to this one; this one returns 200)

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Free to start
Can a solo operator reach it
Yes, without talking to anyone

api_gate, verbatim from the file:

free (custom/remote connectors: Free plan is limited to one custom connector; Pro, Max, Team, and Enterprise get unlimited custom connectors - no separate paid tier just to use the directory)

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

No GitHub organisation could be tied to claude.com with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

5 candidate accounts seen and rejected by the evidence rules: claude-code-expert, claudekit, claudeskills, SuperClaude-Org, claude-world. A name match alone is never accepted; the account has to point at the vendor domain.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

Sources

2 source URLs. Raw sources field, verbatim:

https://claude.com/connectors, https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp

Notes, verbatim from the file
Because each connector is built and operated by its own third-party developer (not Anthropic), the trust/auth posture varies connector-by-connector - Anthropic's role here is curation and the OAuth consent screen, not custody of your credentials.
Provenance
Entry id
07-claude-anthropic-mcp-connector-directory
Source file
07-mcp-infrastructure.md
Source line
204
Tier
RESEARCHED
last_checked
2026-08-24
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.