Shipyard MCP

Created By
shipyard7 months ago
Loop your agents into environment management, and give them access/context to run tests, tail environment logs, start/stop environments, and debug remote issues.
Overview

what is Shipyard MCP?

Shipyard MCP is a command-line interface tool designed for managing ephemeral environments on the Shipyard platform, allowing users to loop agents into environment management and provide them with the necessary context to run tests, tail logs, and debug issues.

how to use Shipyard MCP?

To use Shipyard MCP, install the CLI using the provided installation commands for your operating system, log in to your Shipyard account, and start executing commands to manage your environments.

key features of Shipyard MCP?

  • Manage ephemeral environments with ease.
  • Execute commands to start, stop, and debug environments.
  • Access logs and manage services within environments.
  • Integration with AI assistants for enhanced management capabilities.

use cases of Shipyard MCP?

  1. Automating the management of testing environments for continuous integration.
  2. Debugging remote issues in development environments.
  3. Managing multiple environments for different branches of a project.

FAQ from Shipyard MCP?

  • Can I manage multiple environments at once?

Yes! You can list and manage multiple environments using the CLI commands.

  • Is there a graphical interface for Shipyard MCP?

Shipyard MCP is primarily a command-line tool, but it integrates with the Shipyard platform which may offer a GUI.

  • How do I get support for issues?

You can reach out to support via email or join the community Slack for assistance.

Server Config

{
  "mcpServers": {
    "shipyard": {
      "command": "shipyard",
      "args": [
        "mcp",
        "serve"
      ],
      "env": {
        "SHIPYARD_API_TOKEN": "your-api-token",
        "SHIPYARD_ORG": "your-org"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
shipyard
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago