How to connect an MCP connector to Claude: a step-by-step guide
A step-by-step guide to giving Claude access to your email, drive, and spreadsheets through a connector. What MCP is, how a remote connector differs from a local one, and what to do when the link will not work.
By default, Claude answers questions in a chat window. It does not see your Google Drive, does not read your inbox, and has no idea what lives in your Notion. A connector is the bridge that gives Claude access to your real tools, so it stops giving generic advice and starts working with your actual data.
This guide walks you through connecting a connector step by step, checking that the link actually works, and fixing it when something goes wrong. No code, no terminal: it is all done with a few clicks in settings.
What is a connector, and where does MCP fit in?
A connector is a ready-made adapter between Claude and an outside service: your email, drive, spreadsheets, or task board. Under the hood, connectors run on MCP (Model Context Protocol, the open standard an AI uses to plug into external tools). You do not need to understand MCP to use one, but if you want the mechanics, we have a plain-language explainer: what is MCP.
The idea is simple. Without a connector, Claude is a smart conversationalist that knows a lot in general and nothing about your business. With a connector, it gets hands: it can open the right document, find an email, pull data from a sheet, and act on it right away.
What is the difference between a remote and a local connector?
Connectors come in two kinds, and the kind changes how you set it up.
A remote connector lives in the cloud. The service itself builds it, and you simply grant Claude access through a sign-in window. This is the easiest path, with nothing to install on your computer.
A local connector runs on your own machine and usually matters when you use the Claude desktop app with tools that touch files directly on your device. That needs Claude Desktop and a bit of setup. Beginners almost always get by with remote connectors, so start there.
How do you connect a ready-made connector, step by step?
- Sign in to your account on claude.ai and open your profile settings. Look for the section about connectors or integrations.
- In the connector directory, find the service you need. Popular ones are usually there already: file storage, email, calendar, task boards.
- Click connect on the service you picked. A sign-in window from that service opens, the familiar authorization screen you see when you log into a third-party app with Google.
- Log into your service account and confirm the permissions you grant. Permissions are the list of what Claude may do: read only, or read and change. Read that list instead of clicking through it.
- You land back in Claude, and the connector shows up in your connected list. The bridge is up.
Now you can just ask in chat: find the last email from that contractor, build a list of overdue clients from this sheet, open the offer document and suggest three edits. Claude decides on its own what to fetch through the connector.
How do you check that the link works?
Do not take it on faith, test it on a tiny task. Ask Claude to do something it could not do without the connector: name the three most recent files on your drive, show the subject of your latest email, pull one row from a sheet. If it returns your real data instead of a general answer, the link works.
If Claude is vague or says it has no access, either the connector did not finish connecting or you did not grant the right permissions during sign-in.
What if the connector will not connect?
Take it apart, the fault is almost always in one of three places.
First, permissions. Go back into the connector settings and make sure you allowed access during sign-in instead of closing the window halfway. Disconnecting and reconnecting, granting permissions carefully this time, often fixes it.
Second, the wrong account. It is easy to sign into personal email instead of work email. Check that you connected the exact account that holds the data you need.
Third, the service itself. Sometimes a connector is still in early access or temporarily down. If there is no connect button at all, the service may not be supported yet, and that is not your mistake.
Security: what a connector can and cannot see
A connector sees exactly what you allowed on the permissions step, not one byte more. If you granted read-only access to your calendar, it cannot reach into your email. So do not hand over blanket access to everything: give the minimum the task needs, and widen it later.
You can revoke access at any time, in the same connector settings. Turn a connector off and Claude can no longer see that service. It is worth checking the list every couple of months and removing what you no longer use. We covered how the connector standard itself changed in a separate piece: the new MCP standard.
Want to stop reading and try it yourself? Start with the free materials: AGINE Academy guides and the first free lesson about your digital twin. In fifteen minutes you will see Claude turn from a chat partner into a working tool.
AGINE Academy is an independent product, not affiliated with Anthropic. Claude is a trademark of Anthropic.
Questions
No. A ready-made connector is set up with a few clicks in settings: find the service, click connect, sign into your account, and confirm the permissions. Code is only needed if you build your own connector from scratch.
A connector operates within the permissions you granted during sign-in, and you can revoke access at any time. Grant the minimum permissions for a specific task and do not connect services you do not need.
Pasting is a one-time handoff of a single chunk. A connector gives Claude ongoing access to a service, so it finds the right email or file itself when you ask, and you no longer carry data back and forth by hand.
For remote connectors, no, they work right in the browser on claude.ai. The desktop app is mainly for local connectors that work with files on your own device.