Anthropic engineer Thariq said a capability many users may have missed is that Connectors configured in Claude, including tools such as Gmail, Calendar and Slack, can also be used directly inside Claude Code. The same applies to Artifacts, which means integrations set up on Claude’s web interface do not need to be configured again for terminal-based workflows or interactive experiences.
The shared layer behind that behavior is MCP, short for Model Context Protocol. According to the source article, Connectors are essentially one-click MCP integrations that let Claude access, search and operate on data from services including Gmail, Google Drive, Slack, Notion and GitHub. The article also states that Claude’s connector directory currently includes more than 950 MCP servers.
For developers already using Claude Code, the practical point is straightforward: if a Connector has already been enabled on the web side, the terminal tool can use it without setting up a separate integration stack. Artifacts also supports MCP, allowing those same data sources to be pulled into the interactive interface in real time.
Anthropic engineer Thariq (@trq212) highlighted a use case that, in his view, many people have overlooked: if a user has already set up a Connector in Claude, such as Gmail, Calendar, or Slack, Claude Code can use those same connections directly. The same works in Artifacts.
In practice, that means tools connected through Claude’s web interface do not need to be set up again before they can be used in the terminal-based Claude Code or inside the interactive Artifacts environment.
The shared layer is MCP
The article says the key to this "connect once, use everywhere" behavior is that Claude Code and Connectors share the same open standard, MCP, or Model Context Protocol.
Connectors are described as one-click MCP integrations that allow Claude to access, search, and operate on data from tools including Gmail, Google Drive, Slack, Notion, and GitHub. The article adds that Claude’s connector directory currently lists more than 950 MCP servers.
What this changes for Claude Code users
For developers already using Claude Code, the implication is direct: they do not need to build a separate integration setup just to let terminal tools read content from services such as Gmail or Slack. If the Connector was configured on the web side, it will already work there.
Artifacts also supports MCP, which allows the same data sources to be pulled into the interactive interface in real time. The article presents this as a concrete example of Anthropic treating MCP as infrastructure that works across products.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
