Integration registry

Connect SeaShell to the models and tools your team approves

Every entry names the connection, the SeaShell implementation evidence, and the vendor-recognition status. Test-backed means covered by the SeaShell repository. It does not mean vendor-certified.

Read setup docsView JSON registry

Test-backed

A source path and automated test exist in the SeaShell repository.

Protocol supported

SeaShell implements a documented protocol boundary such as MCP.

Machine readable

The same registry is available at /integrations.json for tools and crawlers.

Local model runtime

Test-backed

Ollama

SeaShell detects an Ollama server on localhost, lists installed chat models, and registers them through its OpenAI-compatible provider path.

Connection
Local HTTP API on port 11434
Data boundary
Local endpoint selected by the user
Vendor recognition
not submitted
Evidence reviewed
2026-08-03
Model discoveryChat inferenceLocal embeddingsCustom endpoint

Ollama has not listed, certified, or endorsed SeaShell. Offline mode must be enabled separately.

SeaShell guide Vendor documentation

Local model runtime

Test-backed

LM Studio

SeaShell falls back to the LM Studio model endpoint on localhost when Ollama is unavailable and registers discovered chat models as a local provider.

Connection
OpenAI-compatible HTTP API on port 1234
Data boundary
Local endpoint selected by the user
Vendor recognition
not submitted
Evidence reviewed
2026-08-03
Model discoveryChat inferenceCustom endpoint

LM Studio has not listed, certified, or endorsed SeaShell. Offline mode must be enabled separately.

SeaShell guide Vendor documentation

Hosted model router

Test-backed

OpenRouter

SeaShell supports OpenRouter as a model provider and sends OpenRouter's public app attribution headers with the cli-agent category.

Connection
OpenRouter API with your OpenRouter key
Data boundary
External hosted provider
Vendor recognition
attribution ready
Evidence reviewed
2026-08-03
Hosted model routingApp attribution headersCLI agent category

No attributed request has been approved or sent. OpenRouter usage is not appropriate until its route matches the organization's data policy.

SeaShell guide Vendor documentation

Tool and context protocol

Protocol supported

Model Context Protocol

SeaShell connects to local and remote MCP servers and exposes discovered tools, prompts, and resources through its terminal workflow.

Connection
Local stdio or remote HTTP transport
Data boundary
The configured MCP server and its credentials
Vendor recognition
not applicable
Evidence reviewed
2026-08-03
ToolsPromptsResourcesLocal and remote transports

Protocol support does not validate every server. Each MCP server inherits the access of its process, tools, and credentials.

SeaShell guide Vendor documentation

Need an integration reviewed?

SeaShell separates implementation evidence from vendor recognition. Request a protocol or model-runtime evaluation and include the deployment boundary your team needs.

Request integration