What are Claude connectors today?
Claude connectors are the integrations that let Claude read from, and sometimes act on, systems outside the conversation, and they come in three forms. The Claude connectors directory lists ready-made connectors built by Anthropic and vendors: Oracle NetSuite and Snowflake each publish one, and Salesforce's arrives in beta through the Salesforce in Claude plugin. Custom connectors are any remote MCP server you host or license, added by URL. Desktop extensions bundle a local MCP server for Claude Desktop.
The form sets who is accountable and where the server runs. A directory listing tells you the vendor built and maintains the connector, not which roles, subsidiaries or ledgers it should reach in your tenant. A custom connector reaches a service Anthropic has not verified, and the server must be reachable over the public internet from Anthropic's IP ranges. A desktop extension runs on the employee's laptop with that machine's privileges.
What can an admin control in Claude for business plans?
On Team and Enterprise plans, Owners and Primary Owners decide which connectors exist in the organization, and members cannot use one until it is enabled. Enabling grants nobody access; each person still signs in to the underlying service, so Claude sees only what that person could already see. The exception is a connector configured with a fixed API key or bearer token, which every member shares, so the service account's permissions become the blast radius.
Owners also set a policy for each connector and each permission inside it: Always allow, Needs approval or Blocked. That organization-wide policy is the outer limit; Enterprise custom roles can narrow it, never widen it. Team and Enterprise admins can authorize supported connectors once through the identity provider, so deprovisioning a user removes connector access. On Claude Desktop, the extension allowlist is off until an Owner turns it on, and MDM or Group Policy can disable desktop extensions outright.
Related: See how dotSolved deploys Claude on your enterprise systems
How do you evaluate a connector for NetSuite, Salesforce or Oracle Fusion?
Evaluate it on six questions: identity, scope, read versus write, logging, retention and vendor status. Identity asks whose credentials the MCP server presents to the business system. Per-user OAuth keeps NetSuite roles and Salesforce sharing rules intact; a shared integration user does not, so an account executive could read every opportunity in the org. Scope asks which objects, subsidiaries, ledgers and periods the connector exposes. A tool that runs arbitrary SOQL or SuiteQL is full read access to everything the credential can see; the NetSuite directory connector ships one beside record create and update tools.
Read versus write asks which tools change data. A tool counts as read-only only when the connector annotates it so, and Anthropic notes that most custom connectors do not, so the admin console cannot tell a balance lookup from a journal posting unless the server declares it. Logging asks where each tool call and its caller are recorded, and whether your SIEM can ingest them. Retention asks what the vendor stores and for how long. Vendor status asks who maintains the server; Anthropic warns that server developers may update tool behavior unexpectedly, and the MCP security best practices forbid passing a client's token through to a downstream API.
What belongs on a connector approval checklist?
A one-page record per connector, with a named owner and an answer to each of the six questions, is enough to approve safely and audit later. It should state the business use, identity model, tools enabled and their policy, write rule, log destination, retention terms, next review date and removal steps. Keep it in the register you use for other integrations, so an auditor finds Claude connectors beside the ERP interfaces they already know.
dotSolved publishes a printable twelve-control Claude connector approval checklist, meant to be completed in one sitting by the connector owner and signed by the system owner. It pairs with the ownership register described in Claude Adoption Needs a Connector Ownership Register and the AI governance framework template. Keep it short on purpose: a review that takes an afternoon gets done, and one that takes a quarter gets bypassed.
Where does a governed semantic-layer MCP server such as Nexatron fit?
Nexatron sits between Claude and the business systems so that a question about bookings, AP aging or gross margin is answered through a certified metric definition and the row-level policies of the person asking, not raw table access. It joins a Team or Enterprise organization as a custom connector, so every admin control above applies. The difference is what the tools expose: governed query tools instead of open SQL, every answer carrying the query that ran, the metric definition used and the policies applied.
Live Nexatron connectors include Oracle Fusion, NetSuite, Salesforce, Sage Intacct, SAP S/4HANA, Microsoft Dynamics 365, HubSpot, ServiceNow, Snowflake, Google BigQuery, Databricks, Amazon Redshift, PostgreSQL, Microsoft SQL Server and MySQL; the current list is on the Nexatron connectors page. The same governed tools serve any MCP client, so Claude, ChatGPT and Copilot users get identical definitions and row-level results. Oracle E-Business Suite is not a Nexatron connector; dotSolved's services team implements and supports that application.
What should you decide before approving the first connector?
Decide three defaults before anyone submits a request: the identity model you will accept, the write policy, and the logging destination. A defensible starting position for ERP and CRM data is per-user identity only, no write tools in the first quarter, and every tool call forwarded to the SIEM. With those defaults written down, most requests become a comparison against a standard, not a fresh debate.
Then approve one connector for one team with a measurable question attached, such as hours the finance close spends on ad-hoc report requests, and measure before and after. If that connector touches NetSuite, Salesforce or Oracle Fusion and you want certified definitions and row-level policies from day one, Book a Demo with the dotSolved AI team, or start with the Claude solutions overview below.