What 33 Claude Connectors Can Change
The consent screen says "Gmail". The tools behind it can send, forward and trash. Here's what 33 common connectors can do, what to set first, and a settings list you can build for your own tools.
By Gabe Pérez. I sell Claude setup to small teams, so I gain when companies connect these. I read each public listing and the maker's documentation, and I didn't test inside the apps. Checked November 1, 2026.
How I read them · CSV and JSON · Cite this · What changed
- connectors
- 33
- listed tools, sorted by hand
- 736
- can send, share, delete or pay, counting the makers' docs (17 on listings alone)
- 26
What stands out
- Only 1 of 33 stays read-only once you count the makers' documentation: Xero.
- 6 more show no write tool on the listing but aren't so simple, because the makers' documentation or an unclear tool says otherwise: Ramp, Microsoft 365, Granola, Fireflies, Intercom, Clio.
- Makers' documentation names 623 tools and abilities the listings don't show, on top of 736 listed. 345 of them are Klaviyo's and Atlassian's.
- 23 of Gmail's 29 listed tools change something. The listing's summary says "Draft replies, summarize threads, & search your inbox."
- 5 list a general write tool whose name doesn't tell you what it reaches, so their counts understate them: Stripe, Salesforce (beta), monday.com, Atlassian (Jira/Confluence), Shopify.
Sort and filter
What it can do
Type of app
Where to start: Blocked for anything that deletes, shares, moves money or has open-ended reach. Needs approval for anything else that changes something. Reads start on Needs approval, then Always allow once you’ve seen them work. Exceptions are marked with the reason. Loosen on purpose, one tool at a time.
Reading the numbers: a plain number is on the public listing. A +number appears only in the maker’s documentation and may not show for you. Red can reach outside the record or be hard to undo. Each tool is filed once, under its most serious power, so a dot means no tool filed there. A ? means I can’t rule it out.
| Connector | Edit | Message | Share | Delete | Money | Open-ended | What it can do, and where to start |
|---|---|---|---|---|---|---|---|
| Intuit QuickBooks # Made by Intuit QuickBooks Listing and docs read | 10 | 3 | · | 3 | 8 | · | Creates, sends and deletes invoices, sends payment links, imports into your books, edits employees. Start with reports. Payroll tools stay blocked until the owner approves a named job, then use Needs approval. The listing's summary never says delete. It says read-only payroll answers, then adds employee and base pay changes. My post on whether to connect it 4 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (74)US customers only. New invoices go live in QuickBooks right away, before any send. You pick which permissions to grant at sign-in, so grant only what you need. Loosen first: company-info and qbo_catalog_search_products: company and product details, no pay data. Set to Blocked (12)
Set to Needs approval (16)
Reads (46): Needs approval at first, then Always allow once you've seen them work
|
| Xero # Made by Xero Limited Listing and docs read | · | · | · | · | · | · | Reads invoices, bills, contacts and bank transactions. No listed tool changes anything. Decide who may read your bank transactions. Xero's other AI connections can write, so use this one. The listing's summary promises financial summaries. Read access also covers bank transactions and contacts. My post on whether to connect it Every tool, and what to set (20)Works on any Xero business plan, with one Xero organization per connection. Xero says read-only "at launch", so recheck the tool list later. Reads (20): Needs approval at first, then Always allow once you've seen them work
|
| Stripe # Made by Stripe Listing and docs read | +1 | ? | ? | ? | +4 | 1 | Reads your account. One general write tool can refund, cancel subscriptions and void invoices. Connect a sandbox first. Keep reads on approval, as Stripe advises. Refunds also need Dashboard approval. The listing's summary never mentions writing, yet one listed tool uses any Stripe write method, and the docs name send-money tools. My post on whether to connect it 3 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (18)Stripe says an owner must add it on Team and Enterprise before members connect. Admins can turn it off for the whole team, and you can set different permissions for live and sandbox accounts when you connect. Loosen first: search_stripe_documentation, if anything: it reads Stripe's public docs and not your account. Set to Blocked (6)
Set to Needs approval (3)
Reads (9): keep on Needs approval, as the maker advises
|
| Ramp # Made by Ramp Listing and docs read | ? | ? | ? | ? | ? | ? | Listed tools read spend, cards, vendors and users. Ramp's docs also approve expenses and lock cards. If sign-in offers Full access or Read-only, pick Read-only, then check for tools beyond the 17 listed. Listed as "read-only", but Ramp's guide describes approvals, card locks and getting card details to buy, and Full access is the default. My post on whether to connect it 2 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (17)Ramp's guide gives a different address from the listing, and no one logged in to check the tools match. Tools depend on your Ramp role and the access level you pick. Read-only hides write tools. Admins can limit users. Set to Needs approval (2)
Reads (15): Needs approval at first, then Always allow once you've seen them work
|
| Gusto # Made by Gusto Listing and docs read | 3+3 | 1 | · | · | 5+1 | · | Runs and changes payroll, changes employee pay, and can link the payroll bank account. Pick who connects it, since that person needs full admin. Keep reads on approval too, as Gusto warns. The tagline says "query and analyze". The tools can also run payroll, link a bank account and create a company. My post on whether to connect it 3 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (74)Connecting needs a Gusto full admin. Gusto says never to turn on automatic tool approval or use other connectors in the same session. You choose data categories at sign-in. Its docs name Pro and Max, not Team. Set to Blocked (8)
Set to Needs approval (8)
Reads (58): keep on Needs approval, as the maker advises
|
| Gmail # Made by Google Listing and docs read | 17 | 3 | · | 3 | · | · | Sends, replies and forwards from your address, trashes mail and creates inbox filters. Pick the mailboxes first. Everything Claude reads or sends uses the address of whoever connected it. The listing's summary mentions drafting, not sending, forwarding or trashing, yet 23 of the 29 tools change something. My post on whether to connect it Every tool, and what to set (29)An Owner must enable it for the organization, and a Workspace admin may need to mark Claude as Trusted. On Team and Enterprise, owners decide if members can skip approval. Claude sees attachment details, not contents. Loosen first: create_draft: a new draft reaches nobody until someone sends it. Set to Blocked (7)
Set to Needs approval (16)
Reads (6): Needs approval at first, then Always allow once you've seen them work
|
| Google Calendar # Made by Google Listing and docs read | · | 3 | · | 1 | · | · | Creates, changes and deletes events, edits attendee lists and answers invitations for you. Try it on your own calendar first, because changing a shared event emails its attendees by default. Creating, changing, deleting or answering an event emails all attendees by default, which the listing's summary never mentions. My post on whether to connect it Every tool, and what to set (9)An Owner or Primary Owner must enable it for the organization. Anthropic says each action needs your approval by default. Google marks this Developer Preview. Loosen first: suggest_time and list_events: they only look, while changes here email attendees by default. Set to Blocked (1)
Set to Needs approval (3)
Reads (5): Needs approval at first, then Always allow once you've seen them work
|
| Google Drive # Made by Google Listing and docs read | 3 | · | 1 | 1 | · | · | Searches and reads files, uploads, updates and trashes them, and shares them with people. Clean up overshared folders first, because Claude reads whatever the signed-in person can. The listing's summary says search, read and upload. Sharing, trashing and updating are also there, and Google's tool reference omits them. My post on whether to connect it Every tool, and what to set (11)An Owner or Primary Owner must enable it for the organization. Google Docs, Sheets and Slides are separate connectors, so set those on their own. Google marks this Developer Preview. Loosen first: get_file_metadata and get_file_permissions: they show details about a file, not its contents. Set to Blocked (2)
Set to Needs approval (3)
Reads (6): Needs approval at first, then Always allow once you've seen them work
|
| Microsoft 365 # Made by Anthropic Listing and docs read | +18 | +10 | · | +7 | · | · | Reads mail, files and Teams chats. With write tools on, it sends mail, deletes files and posts. Decide whether to enable write tools at all. Stay read-only until someone names a job that needs them. Made by Anthropic, not Microsoft. The listing shows 7 read tools, but the guide adds 35 write tools an admin can enable. My post on whether to connect it Every tool, and what to set (42)A Microsoft Global Administrator must consent once, plus a Claude Owner on Team and Enterprise. Consenting again grants write permissions. Eight send and event tools can't be set to Always allow. No personal accounts. Loosen first: outlook_create_draft, if enabled: a new draft reaches nobody until someone sends it. Set to Blocked (9)
Set to Needs approval (26)
Reads (7): Needs approval at first, then Always allow once you've seen them work
|
| Box # Made by Box Listing and docs read | 3+18 | · | +4 | · | · | · | Reads and uploads files. Admin-enabled tools can replace versions and share outside the company. Start in the Box Admin Console, where tools get switched on and off for everyone. The listing shows no sharing tool, but Box documents 4, off until an admin enables them, that can reach outsiders. Every tool, and what to set (54)An admin turns it on in the Box Admin Console. Disabled tools vanish from Claude's list, but there are no per-user or per-group settings. Guardrails need Enterprise Advanced. Set to Blocked (4)
Set to Needs approval (21)
Reads (29): Needs approval at first, then Always allow once you've seen them work
|
| Dropbox # Made by Dropbox Listing and docs read | 4+2 | · | 2 | 1 | · | · | Makes share links, asks outsiders to upload files, and deletes files. Check your plan's recovery window, since that sets how long a deleted file can come back. The listing's summary covers sharing but not delete, which is a listed tool. Dropbox's notes for this server say restore isn't available. My post on whether to connect it Every tool, and what to set (27)A Claude admin must enable it. Dropbox says link recipients must request access, so test one link before trusting that. Its beta server at a different address has other tools. Set to Blocked (3)
Set to Needs approval (7)
Reads (17): Needs approval at first, then Always allow once you've seen them work
|
| Slack # Made by Slack Listing and docs read | 2+6 | 1+2 | · | · | · | · | Posts as you, reads and searches private channels and DMs you're in, and edits canvases. Decide if Claude may read private channels and DMs. Keeping it out also costs it public channel reading. Blocking private search alone doesn't stop private reading: the channel and thread tools read private messages too. My post on whether to connect it Every tool, and what to set (25)Workspace admins approve and manage AI tool connections, with audit logs available. Controlling sign-in through Okta needs Slack Enterprise+ and Claude Team or Enterprise. Loosen first: slack_search_users and slack_read_user_profile: they look up people, not messages. Set to Needs approval (11)
Reads (14): Needs approval at first, then Always allow once you've seen them work
|
| Zoom # Made by Zoom Listing and docs read | 2+2 | +1 | +3 | +1 | · | · | Reads recordings, transcripts and summaries, searches Zoom Chat and Canvas, creates Zoom docs. Decide if Claude may search Zoom Chat. Blocking search_zoom seems to stop that, but loses Canvas search too. The listing's summary talks about meetings, but Zoom's doc adds searching Chat messages, and two listed tools create files. Every tool, and what to set (21)Needs a licensed user on a paid Zoom Workplace plan (Pro or above) and an account owner or admin. Meeting content needs AI Companion turned on, and you must be the host or have been given access. Set to Blocked (4)
Set to Needs approval (5)
Reads (12): Needs approval at first, then Always allow once you've seen them work
|
| Granola # Made by Granola Listing and docs read | +1 | ? | ? | ? | ? | ? | Reads your notes, shared notes and workspace public notes, plus full transcripts on paid plans. On Enterprise, turn off Make changes over MCP in Granola's settings, and transcripts too if notes are enough. Looks read-only, but Granola's "Make changes over MCP" switch is on by default and lets tools move notes in folders. 1 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (11)Free gets 30 days of notes and no transcripts. Only Enterprise admins choose what members can reach, and those limits don't bind admins. The switches are under Settings, Workspace, General, Apps & connectors, MCP access. Set to Needs approval (2)
Reads (9): Needs approval at first, then Always allow once you've seen them work
|
| Fireflies # Made by Fireflies AI Corp Listing and docs read | +2 | · | +3 | · | · | · | Reads user profiles and meeting transcripts, including a snapshot of a meeting in progress. Decide who may read transcripts, since they hold what people said in the room, word for word. Listing shows 3 read tools, but Fireflies' reference lists 19, including sharing meetings with outside emails. My post on whether to connect it Every tool, and what to set (19)Fireflies says its Zero-Day Retention promise doesn't cover data sent to outside platforms through this connection. Its reference also lets tools filter by other users, so test what one member can reach. Set to Blocked (3)
Set to Needs approval (2)
Reads (14): Needs approval at first, then Always allow once you've seen them work
|
| HubSpot # Made by HubSpot Listing and docs read | 12 | · | 3 | · | · | · | Changes CRM records and quotes, publishes blog posts, edits marketing emails and web pages. Decide who owns anything public, since blog posts can go live from here. HubSpot's example is "draft and publish a blog post", and a mismatched author email makes Claude create a new one. My post on whether to connect it 4 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (36)A Super Admin must approve it unless the user is one or has App Marketplace Access. Needs a paid Claude plan. Deletes aren't supported. Changes are logged to the user and the connector in the Audit Log. Loosen first: search_properties and get_properties: they list your CRM's fields, not customer records. Set to Blocked (4)
Set to Needs approval (15)
Reads (17): Needs approval at first, then Always allow once you've seen them work
|
| Salesforce (beta) # Made by Salesforce Listing and docs read | ? | ? | ? | ? | ? | 1 | One general tool runs a growing set of actions: changing records, managing users and permissions. Decide if changes must ever come from Claude. If yes, read the action name in every prompt. Four tools sound small, but they front a growing library, and the real list can't be counted from the listing. Every tool, and what to set (4)An admin must turn it on in Salesforce Setup. Each user signs in with their own permissions. It's a beta service, and the guide doesn't say which plans get it. Salesforce advises trying changes in a sandbox. Set to Blocked (1)
Reads (3): Needs approval at first, then Always allow once you've seen them work
|
| Attio # Made by Attio Listing and docs read | 6+9 | · | +1 | +3 | · | · | Creates and changes CRM records, adds notes and tasks, reads call recordings and full emails. Decide who may read email bodies and call recordings through Claude, since CRM access now includes them. The listing's summary never mentions reading email bodies. The docs list 48 tools against 23 here, including merges and deletes. Every tool, and what to set (48)Attio says writes ask for confirmation, and you get your own Attio permissions. A merge makes both originals unreadable. The docs describe no admin approval step. Set to Blocked (4)
Set to Needs approval (15)
Reads (29): Needs approval at first, then Always allow once you've seen them work
|
| Pipedrive # Made by Pipedrive Listing and docs read | 27 | 1 | 1 | 1 | · | · | Sends drafted email, changes deals, contacts and projects, and reads mail threads. Decide whether this CRM link should reach mail history, since Claude can read people's threads. The listing's summary never mentions sending, yet sendMailDraft sends email. Another tool can likely share a mail thread company-wide. Every tool, and what to set (79)You get your own user's permissions, and actions land in the change log. The product page says every plan, the listing says paid plans, so check yours. No tool guide was found. Set to Blocked (1)
Set to Needs approval (29)
Reads (49): Needs approval at first, then Always allow once you've seen them work
|
| Mailchimp # Made by Intuit Mailchimp Listing and docs read | 5 | · | · | · | · | · | Reads past campaign results, plans email, SMS and social campaigns, saves them as drafts. No listed tool sends, so recheck the tool list when you connect, in case one has appeared. The listing's summary says "Ready to send?", but no listed tool sends. Campaigns land in Mailchimp as drafts. 4 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (12)Connecting needs permission to authorize integrations on both platforms, usually Owner or Admin. Set to Needs approval (9)
Reads (3): Needs approval at first, then Always allow once you've seen them work
|
| Klaviyo # Made by Klaviyo Listing and docs read | 7+93 | 1+2 | +2 | +31 | · | · | Creates campaigns, changes customer profiles, and subscribes or unsubscribes people. Check your tools on connecting: a send_campaign tool means you have more than the core 27, so review again. Listing shows 27, but Klaviyo documents 272 tools, including send and delete. Which you get is untested. 2 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (272)Needs Owner, Admin or Manager to connect. Logs miss some of what Claude read or changed and don't name who connected. The read-only switch needs a connector you add by hand. A sent message can't be undone. Set to Blocked (36)
Set to Needs approval (102)
Reads (134): Needs approval at first, then Always allow once you've seen them work
|
| Intercom # Made by Intercom Listing and docs read | +2 | ? | +2 | +1 | ? | +1 | Reads customer conversations and contacts. Intercom's docs add articles, notes and AI changes. Decide who may read customer conversations, then recheck the tool list on connecting, as the docs list more. All 6 listed tools read, but Intercom's docs say 14, plus tools for its Fin AI agent, one of which can delete with no undo. Every tool, and what to set (19)The directory connector reaches US workspaces only. EU workspaces need a connector added by hand, which an Owner does on Team or Enterprise. Internal notes can't reach customers but can reopen a snoozed conversation. Set to Blocked (4)
Set to Needs approval (2)
Reads (13): Needs approval at first, then Always allow once you've seen them work
|
| Notion # Made by Notion Listing and docs read | 7+17 | +3 | · | +3 | · | · | Creates, changes, moves and duplicates pages and databases, and adds comments. Check whose account connects first, because Claude reaches everything that person can see in Notion. The listing shows no delete tool, but Notion's docs add trashing pages and databases, and calendar edits that notify people. My post on whether to connect it 2 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (38)It acts with your full Notion permissions. Limiting which AI apps members can connect needs Enterprise. Connector search needs Business or Enterprise with Notion AI. Loosen first: get-self and get-users: they look up people, not pages. Set to Blocked (3)
Set to Needs approval (29)
Reads (6): Needs approval at first, then Always allow once you've seen them work
|
| Asana # Made by Asana Listing and docs read | 3+5 | · | · | +1 | · | · | Creates projects and tasks and changes existing tasks. Asana's docs also list a delete tool. Look for delete_task in your settings. Asana documents it and the listing omits it. The listing's summary says "30+ tools", the listing shows 15, and the docs add a delete tool that also removes subtasks. Every tool, and what to set (21)There are no permission levels: connecting grants every tool, limited by what the user can see. Only Enterprise+ or Legacy Enterprise admins can block Claude, in Asana app management. Set to Blocked (1)
Set to Needs approval (8)
Reads (12): Needs approval at first, then Always allow once you've seen them work
|
| monday.com # Made by monday.com Listing and docs read | 13 | 2 | ? | ? | ? | 1 | General write tool with unclear reach, plus notifications, sequences and agent setup. Ask whether anyone needs the general write tool, since blocking it may not stop saved code actions. The listing's summary leads with boards, but the connector can run saved code actions and configure other monday agents. 3 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (33)Admins must install the monday MCP app from the marketplace, on any plan. You can limit it to specific workspaces, and users keep their own permissions. monday's support article wouldn't open, so it wasn't read. Set to Blocked (2)
Set to Needs approval (17)
Reads (14): Needs approval at first, then Always allow once you've seen them work
|
| Atlassian (Jira/Confluence) # Made by Atlassian Listing and docs read | 7+88 | +1 | +7 | +3 | ? | 2 | Edits Jira and Confluence. Its execute tools reach public links, page permissions and code merges. Ask your Atlassian admin to review permission groups, the firmest control on this connector. 21 tools listed, but a few of them open a catalog of about 250, including public page links and code merges. My post on whether to connect it 2 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (121)Org admins grant access by permission group. The Jira delete and manage groups are off by default, and deleting an issue can't be undone. Every tool call goes in your organization's audit log. Set to Blocked (12)
Set to Needs approval (98)
Reads (11): Needs approval at first, then Always allow once you've seen them work
|
| Linear # Made by Linear (Linear Orbit, Inc.) Listing and docs read | 5 | · | · | · | · | · | Creates and changes issues and projects, and posts comments. Decide if anyone needs changes from Claude. Linear has a read-only address, untested here, for everyone else. Every tool, and what to set (22)Linear documents a read-only address (mcp.linear.app/mcp/readonly) and a read-only sign-in option. The listing uses the read-write address. Neither route was tested in Claude. Linear publishes no full tool list. Set to Needs approval (5)
Reads (17): Needs approval at first, then Always allow once you've seen them work
|
| ClickUp # Made by ClickUp Listing and docs read | 18+14 | 2+1 | ? | +3 | ? | +1 | Posts chat messages and comments as you, changes tasks in bulk, replaces whole document pages. Tell the team first: chats and comments from Claude post under their name and notify people. ClickUp's docs disagree: one page says no deletion tools, another documents them. A second "ClickUp" listing is by an individual. Every tool, and what to set (54)Every tool acts with the signed-in user's permissions, on all plans. Updating a document page replaces the whole page by default, and merging tasks has no undo. Set to Blocked (4)
Set to Needs approval (35)
Reads (15): Needs approval at first, then Always allow once you've seen them work
|
| Airtable # Made by Airtable Listing and docs read | 6+7 | · | · | +5 | · | · | Adds and changes records, adds tables and fields, and renames them. Pick which bases to connect, since Airtable lets you add or remove them per integration. The listing has no delete tool, but Airtable's reference documents deleting records and whole tables. 1 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (25)All plans, and access mirrors your Airtable role: Commenter or Read-only users only read. Leaving out write permissions on connecting makes it read-only, if Claude offers that (unchecked). An admin may need to allow it. Set to Blocked (5)
Set to Needs approval (14)
Reads (6): Needs approval at first, then Always allow once you've seen them work
|
| Shopify # Made by Shopify Listing and docs read | 10+8 | ? | +2 | ? | ? | 1 | Once approved, changes prices and stock and makes percent-off codes. Reads customer addresses. Think before approving write access in Shopify: lowering it later means uninstalling and reinstalling. The listing says no sign-in, but managing your own store needs it, and on an unsaved store anyone with the address can edit. My post on whether to connect it Every tool, and what to set (44)Even with write access it can't refund, cancel orders or change plan, payments or taxes. With several stores, start a new conversation after switching, or you may work against the wrong one. Loosen first: get-shop-info and search_docs_chunks: shop basics and Shopify's docs, not customers or orders. Set to Blocked (3)
Set to Needs approval (18)
Reads (23): Needs approval at first, then Always allow once you've seen them work
|
| DocuSign # Made by Docusign Listing and docs read | 3+2 | 3+2 | · | · | · | · | Sends documents for signature, voids envelopes, and starts or cancels agreement workflows. Decide if Claude only reads agreements here. If yes, block the envelope tools as well. updateEnvelope reads like a small edit, but it voids envelopes and looks like the tool that sends drafts. 1 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (27)Two admins must act: a Docusign account admin enables it, then your AI platform admin allows the tools. Sensitive accounts are off by default. Workflow tools need a paid Docusign IAM plan. Set to Needs approval (11)
Reads (16): Needs approval at first, then Always allow once you've seen them work
|
| Canva # Made by Canva Listing and docs read | 5+7 | · | · | · | · | · | Creates and edits designs, imports from a web link, moves items between folders and comments. If designs hold anything confidential, put export on approval. Generating designs can use your AI allowance. In Claude, two tools replace several listed design tools, so settings may not match. Autofill is promised but no tool has the name. Every tool, and what to set (27)Admins can only turn it on or off for the whole team, and turning it off ends existing connections. AI actions may use your monthly Canva AI allowance. Looking up a design can return a shareable edit link. Set to Needs approval (13)
Reads (14): Needs approval at first, then Always allow once you've seen them work
|
| Clio # Made by Themis Solutions Inc. (DBA Clio) Listing and docs read | ? | ? | ? | ? | ? | ? | Reads matters, documents and correspondence. Clio's agent can change records after asking. Read each request from Clio's agent, and never set its reply tool to Always allow. The tool names don't mention matters, time or records. Several hand work to Clio's agent, so the list hides what it can change. 6 more with names that don't settle what they do. They start on Needs approval. Every tool, and what to set (26)Needs the Claude desktop app and a Clio Work license from your Clio administrator. Each tool starts at Needs approval. Record changes need Clio Manage or Grow. Set to Needs approval (6)
Reads (20): Needs approval at first, then Always allow once you've seen them work
|
Not in this table. That doesn't mean a connector can't do it: search only covers these 33 and my notes on them.
Your settings list
Someone built this list for their apps. Changing a box makes it your own and replaces any list you saved here.
Tick "I use this" on the connectors your company uses. What to do for each one appears here, ready to send to whoever owns your Claude account.
Your ticks stay in this browser. The site's analytics records how many boxes were ticked, and never which apps.
Use this data: JSON · CSV, one row per tool with its starting setting and source
How to Change a Connector's Permissions
These are Anthropic's steps as of October 30, 2026.
- In Claude, go to Customize, then Connectors and open the connector.
- Under Tool permissions, choose Always allow, Needs approval or Blocked for a group of tools or a single tool (Anthropic’s guide).
- On Team and Enterprise, an owner can do the same for the whole company, and members can’t override it. Use that version if more than one person works there.
- Then check the app’s side. Restricting a tool in Claude only narrows what the app allows. Revoke access in both places when someone leaves.
How I Read the Listings
I took each public listing's complete tool list from the page's data and sorted the tools by name. Listings publish names and no descriptions, so the sorting is judgment. The CSV shows every call, so you can disagree with one.
- Edit
- Creates or changes records inside the app.
- Message
- Reaches a person: an email, a chat, an invoice, a signature request.
- Share
- Changes who can get at something, or makes a public link.
- Delete
- Deletes something or moves it to the trash.
- Money
- Payroll, payments, payment links, bank connections, refunds or imports into your books.
- Open-ended
- A general write tool. Its name doesn't tell you what it can reach.
- Read
- Looks things up and changes nothing, going by its name.
- Unclear
- The name doesn't settle it, including tools that send feedback to the maker.
- I chose these 33. I looked for 36 apps common at small companies, out of about 1,049 listing pages in Anthropic’s public sitemap on the check date. GitHub, Zendesk and Rippling weren’t among those pages. The directory inside Claude could differ.
- A count measures names and not risk. One open-ended tool can reach more than thirty narrow ones. Salesforce lists four tools, and one of them,
dispatch, is a gateway. The severity sort goes open-ended (with abilities I can’t count), then money, share, message, delete, edit, and each outranks any number of the next. That order is my judgment. - A +number is less certain than a plain one. It comes from the maker’s documentation. Some are exact tool names and some are abilities described in words, and I can’t say which appear in your settings. Klaviyo lists 27 tools and documents 245 more.
- I didn’t connect these apps. Admins can remove tools, plans can change what appears, and listings change. My script compares the listed tools with the live pages. Documentation I checked by hand on the date above.
- Your existing permissions still apply. Most connectors act as the person who signed in. A read tool in a badly shared Drive still reads too much.
- Risk across connectors isn’t in this table. A chat with one connector that reads private files and another that sends can move data out, which no single row shows. Approval on sends is what stands in the way.
Cite this
Gabe Pérez, "What 33 Claude Connectors Can Change," gabezen.com, checked October 30, 2026. https://gabezen.com/connectors/
Each connector has its own link: add #gmail, #slack and so on, using the # beside its name. Tell me if a row is wrong and I’ll fix it and note it under What changed.
What changed
- November 1, 2026: Granola went from 4 listed tools to 8, all reads: meeting and transcript search, folders and attachments.
- October 30, 2026: First check: 33 connectors.