# MCP server examples: local, remote, and multi-app

> Three MCP server examples that show when to use a local stdio server, a protected remote server, or a hosted multi-app connector.

Web version: https://claw-link.dev/learn/mcp-server-examples

An MCP server can be a small local program, a remote service for a team, or a
hosted connector that exposes many apps. The protocol is shared, but the place
where it runs determines who manages credentials, networking, updates, and
availability.

## Example 1: a local filesystem server

A coding agent starts a filesystem MCP server on the same machine over `stdio`.
The server exposes tools such as reading a file, listing a directory, or writing
a generated file. The host launches the process and communicates through its
standard input and output streams.

Use this pattern when the tools need local files or a private development
environment. The operator owns the process, its permissions, and its updates.

## Example 2: a remote internal-data server

An organization runs a remote MCP server over Streamable HTTP. It exposes a
small set of tools that query an internal system, such as a customer database or
deployment status service. Each user signs in before their agent can call it.

Use this pattern when the API is private and access rules belong to the company.
The server must validate incoming tokens and give its upstream systems separate
credentials. See [MCP server authentication](https://claw-link.dev/learn/mcp-server-authentication)
for the difference between those credentials.

## Example 3: a hosted multi-app connector

A person connects Gmail, Notion, or Google Drive in a browser. A hosted service
runs the provider OAuth flow, retains the account connection, and exposes the
supported actions to the agent as MCP tools. The person does not build an OAuth
app or operate a refresh-token job for every provider.

Use this pattern for standard SaaS apps when a third-party connection path is
acceptable. ClawLink is this type of service for its supported catalog. It is
not a replacement for a server that must reach an internal network or expose a
custom company API.

## How to choose

| Need | Best starting pattern |
| --- | --- |
| Read or change files on one machine | Local `stdio` server |
| Reach a company-only API | Remote internal server |
| Connect common SaaS accounts | Hosted multi-app connector |
| Change tool behavior or call a private network | Self-hosted server |
| Avoid operating provider OAuth and token refresh | Hosted connector |

The official MCP architecture allows both local and remote servers. “Remote”
does not mean “hosted connector,” and “self-hosted” does not mean “more
permissions.” Those labels describe operation and network placement; provider
scopes still decide what a tool can do.

## Keep reading