# Connect MCP Servers to SeaShell (2026)

> SeaShell supports local stdio and remote HTTP MCP servers, including tools, prompts, resources, timeouts, and remote OAuth flows.

SeaShell is an MCP client in 2026. It connects to local stdio servers and remote HTTP servers, discovers tools, prompts, and resources, and exposes them through the SeaShell terminal workflow. Remote servers can use OAuth when supported. Each server remains a separate trust and data boundary that the organization must review.

## Key takeaways

- SeaShell supports local stdio and remote HTTP MCP connection classes.
- MCP tools, prompts, and resources are discovered from each configured server.
- Remote OAuth, request timeouts, and server lifecycle handling are implemented.
- MCP compatibility is protocol support, not a certification or blanket approval of every server.

## Supported MCP surfaces

SeaShell handles 3 core server surfaces: tools for actions, prompts for reusable instructions, and resources for retrievable context.

Local servers launch through stdio. Remote servers connect through HTTP transport, with OAuth discovery and callback handling when configured. SeaShell also tracks connection status, request timeouts, and server changes.

## Trust boundary

Every 1 MCP server can read or change only what its process, credentials, and exposed tools allow, so scope each integration deliberately.

Use least-privilege credentials, review the server's code and operator, and keep high-risk actions behind SeaShell permission prompts. A remote MCP server can create an external data route even when the selected model is local.

## Compatibility status

The 2026 registry labels MCP as protocol supported because SeaShell implements the client boundary, not because every extension or third-party server has been certified.

SeaShell does not claim inclusion in an official MCP client matrix until an external listing is visible. Test each required server and protocol feature against the SeaShell version approved for the organization.

## Setup

1. Identify a trusted MCP server and document the data and actions it can access.
2. Run seashell mcp add and choose a local command or remote URL.
3. Inspect the saved connection with seashell mcp list.
4. For a remote server that requires OAuth, run seashell mcp auth <name>.
5. Use seashell mcp debug <name> and a low-risk test before enabling production credentials.

## FAQ

### Is SeaShell an MCP client?

Yes. SeaShell connects to configured MCP servers and exposes discovered tools, prompts, and resources in its terminal workflow.

### Does SeaShell support remote MCP servers?

Yes. SeaShell implements remote HTTP transport and OAuth flows, alongside local stdio server processes.

### Does MCP support make every server safe to use?

No. Each server has its own operator, code, credentials, tools, and data routes. Review and scope each one before use.

### Has the MCP project issued SeaShell vendor recognition?

SeaShell makes no certification claim. The public status means SeaShell implements and tests the protocol client boundary; external listings are tracked separately.

## Sources

- [Model Context Protocol architecture overview](https://modelcontextprotocol.io/docs/learn/architecture) (Model Context Protocol)

---

Canonical HTML: https://seashell.sh/resources/integrations/model-context-protocol
Source of truth: aeo_pages row `/resources/integrations/model-context-protocol` (segment: Integrations) (this file is generated from it, never hand-edited).
Licence: SeaShell is proprietary with a free core. It is not open source and there is no public source repository.