Skip to content

Claude connectors guide

Claude connectors for enterprise data

Enterprise guide to Claude connectors: how they work, what data Claude can access, Team and Enterprise admin controls, and the best connectors by system.

Short answer

Claude connectors let Claude read data and take actions in other applications. Remote connectors use the Model Context Protocol (MCP). On Team and Enterprise plans an Owner enables each connector for the organization, and each user then signs in to it, so Claude inherits that user’s permissions in the connected service. The best connectors for enterprise data are the ones that keep those permissions intact and give consistent answers across systems.

Updated

How Claude connectors work

A connector gives Claude a set of tools from another service: search a drive, read a ticket, run a report, update a record. Remote connectors are MCP servers that Anthropic’s cloud connects to on your behalf, which is why Claude’s help pages say a custom connector must be reachable over the public internet from Anthropic’s IP ranges, so a server behind a firewall must allowlist them (Anthropic: custom connectors).

Connectors come from two places. The Connectors Directory lists connectors with a page for each that describes its use cases and read and write capabilities. Custom connectors are any remote MCP server you add by URL. Anthropic’s help center says custom connectors are available on Free, Pro, Max, Ultra, Team and Enterprise plans, with Free limited to one, and that custom connectors can reach services that Anthropic has not verified (Anthropic: connectors).

Once a connector is added, Claude decides when to call its tools during a conversation, and asks for approval according to the tool permissions set by the user or the organization.

What data Claude can access through connectors

This is the question security teams ask first, and the answer depends on how the connector authenticates.

  • Connectors where each user signs in. Anthropic’s help pages say Claude inherits the permissions the user already has in the connected service. A user who cannot open a record in the source system cannot retrieve it through Claude.
  • Connectors set up with one credential for everyone. Anthropic also notes that a connector configured with a single credential reaches whatever that credential can access, for everyone who uses it. For business data this is the setup to avoid.
  • What the server itself exposes. A connector can only return what its MCP server’s tools return. A file-search connector reaches documents; a connector over a data platform can reach every table its credential can query.

For enterprise data, choose connectors where users sign in with their existing account in each system, or through the company’s SSO, so existing role-based access, row- and column-level security and sharing rules keep applying.

Admin controls on Claude Team and Enterprise

Anthropic’s help pages describe these controls for organization Owners (checked 2026-11-19):

  • Enable per connector. Owners add a connector in Organization settings under Connectors. Enabling it does not grant anyone access; each user still authenticates.
  • Tool permissions. Owners can set each category of tools to always allow, needs approval or blocked, for the whole organization. Users cannot override it, and Enterprise custom roles can restrict it further.
  • Read-only where it matters. Owners can limit a connector to reading data, with no write-back.
  • Requests. Users can request a connector from its directory page so Owners review it before it is enabled (on by default for Team; an Owner turns it on for Enterprise).
  • Data handling. Connected services process data under their own terms, so review each provider the way you would any other SaaS vendor.

Write these decisions down before rollout: which connectors are approved, which tool categories need approval, and who reviews requests.

The best Claude connectors for enterprise systems, by category

Productivity connectors for mail, calendars and documents are the usual starting point. The harder and more valuable questions sit in systems of record. These are the systems enterprise teams ask about most, with what a good connector for each should handle:

Many vendors list their own connectors in Claude’s directory, and they are a good fit for questions about that one system. Check the directory for the current list. For questions that span systems, or that must use the same definition of revenue everywhere, a governed layer such as Nexatron sits alongside them. Browse every connector or start from a category such as ERP and accounting.

Popular connectors in Claude’s directory

These vendor-built connectors are listed in Claude’s Connectors Directory, described from each listing page (read 2026-11-19). Nexatron reaches the same systems for governed, cross-system questions; those links are marked “via Nexatron”.

Popular vendor connectors in Claude’s Connectors Directory
ConnectorWhat the listing says it coversDirectory listingVia Nexatron
NotionSearch pages and databases, create and update pages and tasksclaude.com/connectors/notionNotion via Nexatron
AtlassianSearch, read and update Jira, Confluence and Bitbucketclaude.com/connectors/atlassianJira and Confluence via Nexatron
HubSpotSearch and update contacts, companies, deals and campaignsclaude.com/connectors/hubspotHubSpot via Nexatron
GreenhouseSearch and update candidates, jobs, interviews and offersclaude.com/connectors/greenhouseGreenhouse via Nexatron
SnowflakeRetrieve structured and unstructured data through SQL and Cortex agentsclaude.com/connectors/snowflakeSnowflake via Nexatron
Databricks GenieNatural-language questions over data under Unity Catalog permissionsclaude.com/connectors/databricksDatabricks via Nexatron
BoxSearch and edit files under Box permissionsclaude.com/connectors/boxBox via Nexatron
Google DriveSearch and read Drive files, including Docs, Sheets and PDFsclaude.com/connectors/google-driveGoogle Drive via Nexatron
StripeCall the Stripe API and search Stripe documentationclaude.com/connectors/stripeStripe via Nexatron
SentrySearch and debug errors and issuesclaude.com/connectors/sentrySentry via Nexatron
LinearManage issues, projects and cyclesclaude.com/connectors/linearLinear via Nexatron
IntercomConversations, tickets and contact dataclaude.com/connectors/intercomIntercom via Nexatron

The directory changes often; browse Claude’s connectors and plugins for the current list.

Custom Claude connectors: when to build or add one

Add a custom connector when the system you need is not in the directory, or when your organization runs its own MCP server. On Team and Enterprise plans, Owners add it under Organization settings, Connectors, Add, then Custom, then Web, and enter the server URL. The server must support remote MCP. Most use OAuth sign-in.

Before you build one yourself, list the work: OAuth with each system, mapping the system’s permission model, pagination and rate limits, and tool descriptions good enough that Claude picks the right tool. For a single internal API that is reasonable. Across an ERP, an HR system and a CRM it becomes an ongoing engineering commitment.

How to add a custom connector in Claude

  1. Confirm the server URL with the team that runs the MCP server, and that it is reachable from Anthropic’s IP ranges.
  2. On Team or Enterprise, an Owner opens Organization settings, then Connectors, then Add, then Custom, then Web. On Pro or Max, open Customize, then Connectors.
  3. Enter a name and the remote MCP server URL, and choose how users sign in (most servers use OAuth).
  4. Set tool permissions: always allow for read tools you trust, needs approval or blocked for anything that writes.
  5. Each user opens the connector and signs in with their existing account, then starts a conversation with it enabled.
  6. Ask one narrow question and check the result against the source system before rolling it out.

Where Nexatron fits

Nexatron is listed in Claude’s Connectors Directory as a community connector: claude.ai/directory/nexatron. Adding Nexatron once gives Claude governed access to every system your Nexatron workspace has connected. Users sign in with their existing account in each system, or through the company’s SSO if it has one, and Nexatron inherits their existing permissions, so every answer contains only data they’re already authorized to see.

Answers use your approved definitions and show the definition, source and query behind each number, and one question can combine systems such as Salesforce and Snowflake. If the directory is not available to your organization, add https://api.nexatron.io/api/v1/mcp as a custom connector. The Claude setup page has both paths step by step.

Frequently asked questions

What are the best Claude connectors for enterprise data?
The best are the ones that keep each user’s existing permissions and give consistent answers: connectors for your CRM, ERP, HR system, service desk and data platform where users sign in with their existing access. A governed layer such as Nexatron covers many systems through one connector.
What data can Claude access through connectors?
Only what the connector’s tools return. When each user signs in, Claude inherits that user’s permissions in the connected service. A connector set up with one credential for everyone reaches whatever that credential can access, which is why enterprises prefer user-level sign-in.
Who can add connectors on Claude Team and Enterprise?
Organization Owners enable connectors for the organization, and can set tool permissions to always allow, needs approval or blocked. Enabling a connector does not grant access by itself; each user authenticates to it.
What is a custom Claude connector?
A remote MCP server added to Claude by URL rather than from the Connectors Directory. It must be reachable from Anthropic’s cloud, and custom connectors can reach services that Anthropic has not verified, so admins should review each one.
Is Nexatron in Claude’s Connectors Directory?
Yes. Nexatron is listed in Claude’s Connectors Directory as a community connector at https://claude.ai/directory/nexatron. It can also be added as a custom connector with the server URL https://api.nexatron.io/api/v1/mcp.
Can Claude answer questions across several business systems at once?
Yes, if a connector can combine them. Nexatron answers one question across connected systems, for example Salesforce opportunities with Snowflake usage, and shows the query it ran in each source.

Sources

Statements about other products come from these public pages, read on November 19, 2026.

Bring Claude to your systems of record

Tell us the systems and questions that matter. We show governed answers in Claude under your users’ existing permissions.