# Effective Patterns for Advanced MCP Usage

Discover the power of MCP with multiple server and client connections.

- **Source:** [O'Reilly Radar](https://www.oreilly.com/radar)
- **Topic:** [Data & AI](https://brifing.si/c/data-ai)
- **Original article:** <https://www.oreilly.com/radar/?p=19477>
- **On Brifing:** https://brifing.si/s/a102fea0-e2b3-4d59-acac-8048d06459aa

## Basic MCP Usage

Basic MCP usage typically involves connecting a single server to a single client. For example, connecting a Gmail MCP server to Claude Code. This allows functions like sorting emails, drafting replies, and finding old emails. However, since Gmail's own interface already provides these functions, this usage remains limited.

## Multiple Server Connections

The real power of MCP emerges with multiple server connections. For instance, a Gmail MCP server can upload receipts to a service provider like Benepass. This enables cross-application tasks that a single app couldn't handle. Server composition is one of MCP's most significant features.

## Multiple Client Connections

Another advantage of MCP is the ability to connect multiple clients. For example, while using Claude Code in the terminal, the same servers can connect to other interfaces like Slack or Linear. This provides access to the same integrations across different platforms and speeds up workflows.

## Limitations of Local Servers

Local servers are often complex for users, requiring steps like npm installation, JSON file editing, and environment variable setting. Remote servers are easier; just paste a URL. Therefore, remote servers should be preferred over local ones.

## Transitioning to Remote Servers

Bridges like mcp-auth-wrapper can convert local servers to remote, multi-tenant servers. This makes sharing easier, with OAuth on the front end and user credentials on the back end.

## Simplifying the Configuration Process

Services like install-mcp can simplify the configuration process by providing the correct installation link and per-client instructions. Additionally, TypeScript libraries like mcp-install-instructions can integrate this process.

## Centralized Configuration and Authentication

Each user configuring and authenticating each MCP server independently leads to unnecessary repetition. Tools like mcp-aggregator solve this by providing a single endpoint and login, with every tool namespaced behind it.

## MCP Gateway and Enterprise Needs

An MCP gateway can add features like SSO integration and IT admin controls for enterprise needs. mcp-aggregator offers a minimal DIY version for these requirements, including the ability to use MCP server configurations as per-session constraints.

## The Future of MCP

Future developments in MCP may include more integrations and standardization. Standardizing the mcp.json file format could further simplify this process. Features like enterprise-managed authentication could also become more widespread.

## Conclusion and Recommendations

MCP's multiple server and client connections significantly speed up workflows and increase efficiency. Remote servers should be preferred over local ones, and the configuration process should be simplified as much as possible. Centralized configuration and authentication reduce repetition and improve user experience.

## Sources covering this story

- https://www.oreilly.com/radar/?p=19477 — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._