Requesting a Claude Connector
Claude Enterprise supports connectors — integrations that let Claude read from and work with third-party tools through the Model Context Protocol (MCP). The Microsoft 365 connector searches your SharePoint files and Teams content; the Atlassian connector reads Jira tickets and Confluence pages. ITS enables connectors at the organization level. Once one is enabled, you connect your own account and toggle it on or off in your Claude settings.
Approved Connectors
Connector | Status | Notes |
|---|---|---|
Adobe for creativity | Approved | Adobe Creative Cloud and Express assets |
Adobe Workfront | Approved | Work and project management |
Asana | Approved | Project and task management |
Atlassian | Approved | Jira issues and Confluence pages |
bioRxiv | Approved | Preprint search (life sciences) |
ChEMBL | Approved | Bioactive molecule and drug discovery data |
Clinical Trials | Approved | ClinicalTrials.gov study records |
GitHub Integration | Approved | Repositories, issues and pull requests |
Google Workspace | Not Approved | Syracuse’s Google Workspace tenancy currently lacks the necessary auditing features. |
Granola | Approved | Meeting notes and transcripts |
Microsoft 365 | Approved | Outlook, SharePoint, OneDrive and Teams |
Microsoft Learn | Approved | Microsoft technical documentation |
Midpage Legal Research | Approved | Legal research and case law |
monday.com | Approved | Work management boards |
Nexus Connect (Beta) | Approved | Nexus data access — beta |
PubMed | Approved | Biomedical literature search |
Salesforce sObject Reads | Approved | Read-only Salesforce record access |
Scite | Approved | Citation context and research evaluation |
Zoom for Claude | Approved | Meeting recordings and transcripts |
Approved — Enabled in Claude Enterprise. Connect your own account under Settings > Connectors.
Under review — Request received; ITS is evaluating vendor documentation. Not yet available.
Not approved — Reviewed and declined under current policy.
The live list is always visible in your Claude settings under Connectors.
If a Connector Is Not Available
While a connector is under review — or if the tool you need has no Claude connector at all — you can still work with it today.
Cowork with Claude in Chrome. Cowork paired with the Claude in Chrome browser extension lets Claude see and act on the pages open in your browser. Because you stay signed in as yourself, Claude works within the access you already have and can read data, fill forms and complete tasks in nearly any web-based application, connector or not. Claude asks for your approval before taking consequential actions, and you can watch each step as it happens. Cowork is also available directly in the Chrome side panel.
Local MCP in Claude Desktop. Claude Desktop supports local MCP connections that run entirely on your machine without sending data to a third-party server. This suits tools that expose a local integration.
Neither approach grants Claude access beyond what your own account already has, and University data handling policies still apply. Treat anything Claude reads or writes in these sessions the same way you would treat it in the application itself.
How to Request a New Connector
Email aihelp@syr.edu with:
The connector name and a link to the vendor’s connector or MCP documentation
Your business use case — what you plan to do with the integration and what problem it solves
Confirmation of a University contract with the vendor, if applicable
The vendor’s SOC 2 Type II report, attached if you can obtain it
What ITS Reviews
SOC 2 Type II report — Required. Requests stay on hold until the vendor provides one. Many vendors publish it on a trust page; otherwise ask your account representative.
Existing University contract — Vendors already under contract are easier to approve.
Data classification risk — Connectors that could expose Confidential data such as FERPA records, HIPAA data, PII or financial information face a higher bar and may need additional security review.
Breadth of use — Because connectors are enabled organization-wide, ITS weighs how many people benefit. Highly specialized tools may be deprioritized.
Vendor maturity — Early-stage or experimental MCP implementations may be held until they stabilize.
Frequently Asked Questions
How long does the review take?
It depends on how quickly vendor documentation can be obtained. Requests with a SOC 2 report already in hand may resolve in a few business days. Complex reviews take longer.
What if my vendor has no SOC 2 report?
ITS will help assess alternatives, but some requests are not approvable under current policy.
Questions?
Reach out to the AI team at aihelp@syr.edu or book a consultation at the AI at Syracuse University Bookings page.