# Connectors & plugins: bring your tools to the assistant with MCP

> More AI ships a browsable catalog of over 160 verified MCP connectors — GitHub, Notion, Linear, Stripe and many more — plus local plugins in the same .mcpb format as Claude Desktop extensions. Here is how to connect them and keep every permission under your control.

https://more-ai.net/guides/connectors-mcp · Updated October 26, 2026

## What a connector is

An MCP connector is a bridge between the assistant and a tool you already use, built on MCP—the open Model Context Protocol. Connect one and its actions become tools the agent can call in Home and Code: read a Linear issue, update a Notion page or look up a Stripe customer while working.

Because MCP is an open standard, you’re not limited to what ships in the box: any remote MCP server can be added in a couple of clicks.

## Browse the catalog

Settings → Connectors opens a browsable directory of over 160 verified remote MCP servers across nineteen categories — software development, project management, CRM, payments, productivity, design, databases, search and more, each with its real logo so you can find tools at a glance.

Connecting is one click plus the sign-in the service itself asks for: OAuth where the provider supports it, an API key where it doesn’t, and nothing at all for open servers.

![The connector catalog with categories and one-click connect](https://more-ai.net/screenshots/en/connectors.png)

## Local plugins: .mcpb files

Not everything should be a remote service. Plugins are local MCP servers installed from a .mcpb file — the same format as Claude Desktop extensions — so the ecosystem built for Claude Desktop works here too. A plugin adds tools that run right on your machine, with no server setup.

Drop the file in, review what the plugin provides, and its tools join the same permission system as everything else.

## Permissions you actually control

Every connector tool has a per-tool setting: Always allow, Needs approval, or Off. The defaults are sensible — actions that only read run freely, actions that change data ask first — and you can tighten or relax each one individually.

Scheduled routines are stricter still: each routine gets an explicit list of connectors it may use, so an unattended run can never reach a tool you didn’t hand it.

## The security model

For local desktop workflows, connector credentials can remain encrypted on your computer and calls can go directly from it to the connected service. If you use a connector in a cloud, web or mobile workflow, More AI may process and store the credentials and data that feature needs on its infrastructure. Content fetched from the web is treated as untrusted: instructions hidden in a fetched page are not followed as commands, which is the guard against prompt-injection.

## Ideas to steal

A few patterns that pay off quickly:

- Triage: read the newest issues from your tracker and draft responses in one pass.
- Docs that stay current: after a work session, have the assistant update the Notion or Confluence page.
- Support digest: search your helpdesk inbox for a topic and summarize what customers actually said.
- Payments lookup: pull up a customer’s subscription state without leaving the conversation.

## Gmail, Google Drive, Docs, Sheets and Calendar

More AI also offers direct Google connections alongside MCP connectors. Where available in Settings → Connectors, choose Gmail, Google Drive or Google Calendar, then review the permissions shown by Google. A connection belongs to your More AI account. Google Docs and Google Sheets use the Drive connection; they do not need separate connections.

Gmail tools can search and read messages, prepare drafts and send mail within your task permissions. Drive tools can find and read existing files, create and organize files, and edit supported Docs or Sheets; broad Drive access can include existing files throughout your Drive. Calendar tools can read events, create or update them and respond to invitations. Features depend on your account, app version, enabled tools, supported formats and Google permissions.

Google requests pass through More AI’s connector servers, including for local desktop tasks. Content needed for a task may reach its AI provider and remain in a conversation or synced work. AI Observability and session replay may also capture copies according to your privacy settings. Read the Privacy Policy before using sensitive data. Disable or disconnect a service in Settings → Connectors, or revoke access in your Google Account; disconnecting does not delete earlier conversations or files.

- [How Google data is handled](https://more-ai.net/privacy)

## Frequently asked questions

### What is MCP?

The Model Context Protocol — an open standard that lets AI apps talk to external tools. More AI uses it for both remote connectors and local plugins, so anything that speaks MCP can become a tool the assistant may call.

### Can I use Claude Desktop extensions in More AI?

Yes — plugins install from .mcpb files, the same format Claude Desktop uses for its extensions, so that ecosystem carries over. A plugin runs locally on your machine with no server setup.

### Do connectors get access to my data?

For MCP connectors, it depends on where the workflow runs. Local desktop calls can go directly to the connected service with credentials encrypted on your computer. Cloud, web or mobile workflows may require More AI to process and store the credentials and data needed by that feature. By default read actions run freely and write actions ask first; you can change that policy or turn any tool off entirely. Direct Google connections use More AI connector servers even for local desktop tasks, as explained in the Google-services section above.

### Can scheduled routines use connectors?

Yes, but only the ones you explicitly allow per routine — an unattended run can never reach a connector you didn’t hand it.

### My tool isn’t in the catalog — can I still connect it?

Yes. Add any remote MCP server by its URL in a couple of clicks, or install a local plugin from a .mcpb file. The catalog is a curated starting point, not a limit.

## More guides

- [Control what the agent can do: tools & permissions](https://more-ai.net/guides/agent-tools.md): More AI’s agent can read and write files, run commands, search the web, schedule routines and connect to other apps. Every capability can be switched off; command approvals then follow the selected access mode.
- [Projects: turn any folder into an AI workspace](https://more-ai.net/guides/cowork-projects.md): A project binds the desktop assistant to a folder on your disk, edits with visible diffs and creates Word, Excel and PowerPoint deliverables. Signed-out work does not sync; after sign-in, project sync is on by default unless you disable it.
- [Scheduled AI tasks: local routines and cloud check-ins](https://more-ai.net/guides/scheduled-routines.md): Create one-off or recurring AI tasks, choose local or cloud execution, and review their results. Practical ideas for research, page checks and weekly reports, with clear schedule and file-access limits.

---

More AI — One AI agent for documents, research and code — on desktop, the web, the terminal and your phone, with your own API key at your provider’s price.

- Download: https://more-ai.net#download
- Docs: https://more-ai.net/docs.md
- Guides: https://more-ai.net/guides
- llms.txt: https://more-ai.net/llms.txt
