Tugboat MCP Server

Created By
Lullabota year ago
A Model Context Protocol (MCP) server for interacting with the Tugboat API.
Overview

What is Tugboat MCP Server?

The Tugboat MCP Server is a Model Context Protocol (MCP) server designed for interacting with the Tugboat API, enabling AI assistants to access and manipulate Tugboat resources through a standardized interface.

How to use Tugboat MCP Server?

To use the Tugboat MCP Server, clone the repository, install dependencies, and set up environment variables such as TUGBOAT_API_KEY. You can then run the server and interact with it through AI assistants like Claude or Cursor.

Key features of Tugboat MCP Server?

  • Access Tugboat projects, previews, and repositories.
  • Create, build, refresh, and delete previews.
  • Search for Tugboat resources and view preview logs.
  • Support for both stdio and HTTP transports with authentication.

Use cases of Tugboat MCP Server?

  1. Managing Tugboat projects and previews through AI assistants.
  2. Automating interactions with the Tugboat API for CI/CD workflows.
  3. Facilitating seamless integration of AI tools with Tugboat resources.

FAQ from Tugboat MCP Server?

  • What is the Model Context Protocol (MCP)?
    MCP is an open protocol that allows AI assistants to integrate with external data sources and tools seamlessly.

  • Is the Tugboat MCP Server free to use?
    Yes, the Tugboat MCP Server is open-source and free to use.

  • What programming languages are supported?
    The server is built using Node.js, making it compatible with JavaScript and TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Lullabot
Star
1
Language
HTML
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)

2 days ago