MCP Connectors: A Growing Catalogue, Guided Setup, and Verified Connections

V7 Go reaches more than forty systems through MCP, and connectors are added regularly. Connecting one is a guided flow now: browse the catalogue, fill in what the connector asks for, and see the connection verified before you rely on it.

The catalogue exists so that connecting a familiar tool is a short job rather than a project. Each connector in it has already been set up against V7 Go, so what is left to you is a short form rather than a server to wire up. Anything not in the catalogue can still be added as a custom connector.

Setting one up

• Browse, do not hunt: The catalogue lists what is available with a page per connector, so finding the right one does not start with knowing its name.

• The connection is verified, not assumed: A connect attempt is checked and the result reported back, and a failure is stored with its error rather than leaving you to guess why nothing works.

• A credential form that checks itself: Each connector asks for what it needs in a form that validates the input as you fill it, rather than accepting anything and failing later.

• Fewer steps that do not apply: OAuth client setup is optional rather than required, failed tool loading can be retried, and a streamed response is matched to the request that asked for it.

• Connectors come first in tool search: Tool search surfaces MCP connectors ahead of other results, so what you connected is what you find.

What is in the catalogue

• Deals and CRM: Affinity, Apollo.io, Attio, Clay, HubSpot and Pipedrive.

• Market and portfolio data: Capital IQ, PitchBook and Yardi.

• Documents, storage and knowledge: Airtable, Box, Coda, Dropbox, Egnyte, Glean, Google Docs, Google Drive, Google Sheets, Google Slides and Notion.

• Email, chat and calls: Fireflies.ai, Gmail, Gong, Google Calendar, Google Chat, Google Contacts, Granola, Intercom, Intercom (EU), Slack and Work IQ.

• Projects and engineering: Asana, Atlassian Rovo, ClickUp, Figma, GitHub, LaunchDarkly, Linear and Monday.com.

• Contracts and payments: PandaDoc, PandaDoc (EU) and Stripe.

The list keeps growing. New connectors go in as they are built, so it is worth a look even if the tool you wanted was missing last time.

Anything else, as a custom connector

A niche or in-house tool does not have to wait for the catalogue. The custom MCP connector action sits in the top bar: point it at the server and it works alongside the rest. The catalogue is the short path for the tools most teams already use, not the boundary of what V7 Go can reach.

Once it is connected

• Tools are scoped to their connector: Tools are discovered per connector and carry a stable identity, so a tool name means the same thing from one run to the next.

• Connector names survive the handoff: A connector name, and a mention that cannot be resolved, are both preserved rather than quietly dropped.

• Tool use is recorded as activity: An MCP tool invocation is logged as user activity, with the origin and the sign-in route behind it, so a review can answer who used what.

• Versions are pinned and visible: The component version behind a workflow is recorded and shown, and a skill pinned to an out-of-date version is flagged before it breaks.

Availability

The catalogue is under Integrations, in MCP connectors, along with the custom connector action.