Connected Mcp Module

General-purpose MCP connection module for linking custom browser automation services and third-party integrations to Claude Code.

When to Use This MCP Server

Connect this server when you need to:

• Bridge a custom or proprietary browser automation service into the Claude Code MCP ecosystem with a standardized interface
• Connect multiple disparate automation tools under a single unified MCP protocol endpoint
• Create a reusable connection layer that abstracts away transport details for downstream browser automation consumers

Consider alternatives when:

• A dedicated MCP server already exists for your specific tool such as Playwright, Puppeteer, or Browserbase
• You need a simple, single-purpose automation setup rather than a multi-tool connection framework

Quick Start

Configuration

Copy
name: connected-mcp-module
type: mcp
category: browser_automation

Example Connection

Copy
claude mcp add connected-mcp-module -- npx connected-mcp-module@latest

Available Tools

connect:          Establish a connection to a target automation service
execute-action:   Run a named action on the connected service
query-state:      Retrieve current state from the connected module
disconnect:       Cleanly terminate the connection to the service
list-capabilities: Enumerate available actions from the connected service

Core Concepts

Connection Module Overview

Aspect	Details
Protocol	MCP over stdio or SSE transport
Purpose	Unified bridge for heterogeneous automation backends
Connection Types	WebSocket, HTTP, gRPC, and stdio adapters
State Management	Connection pooling with automatic reconnection
Extensibility	Plugin architecture for adding new backend adapters
Error Handling	Automatic retry with exponential backoff

Module Integration Architecture

┌─────────────┐     ┌──────────────────┐     ┌────────────────┐
│ Claude Code  │────▶│  Connected MCP   │────▶│  Backend A     │
│  (Client)    │◀────│    Module        │──┐  │  (Browser)     │
└─────────────┘     └──────────────────┘  │  └────────────────┘
                                          │  ┌────────────────┐
                                          └─▶│  Backend B     │
                                             │  (Scraper)     │
                                             └────────────────┘

Configuration

Parameter	Type	Default	Description
backend_url	string	required	URL or address of the target automation backend
transport	string	stdio	Transport protocol: stdio, sse, or websocket
retry_count	integer	3	Number of automatic retry attempts on connection failure
timeout_ms	integer	30000	Connection and request timeout in milliseconds
auth_token	string	optional	Bearer token for authenticated backend connections

Best Practices

1. Define Clear Backend Contracts - Document the expected API surface of each connected backend. The module acts as a bridge, so mismatched expectations between Claude Code and the backend will cause silent failures.

2. Use Connection Pooling - For backends that support concurrent requests, enable connection pooling to reuse established connections. This reduces latency and avoids the overhead of repeated handshakes.

3. Implement Health Checks - Configure periodic health checks against connected backends to detect failures early. The module should automatically reconnect when a backend becomes available again.

4. Log All Connection Events - Enable verbose logging for connection establishment, disconnection, and retry events. These logs are essential for diagnosing intermittent connectivity issues in distributed setups.

5. Version Your Backend Adapters - When updating backend integrations, version the adapter interface to maintain backward compatibility. This prevents breaking existing workflows when new features are added.

Common Issues

1. Connection Refused - The target backend is not running or is not accepting connections on the specified URL. Verify the backend process is active and the URL matches the listening address.

2. Transport Mismatch - Using SSE transport with a backend that only supports WebSocket will fail silently. Confirm the transport type matches what the backend server expects.

3. Authentication Timeout - Token-based authentication may fail if the token has expired. Implement token refresh logic or generate long-lived tokens for persistent connections.