# asyntai/mcp-bridge [Health: Active]

**Category:** 🗣️ Conversational AI  
**Repository:** https://github.com/asyntai/mcp-bridge  
**GitHub Stars:** 1  
**npm Downloads (last month):** 154  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/asyntai-mcp-bridge

## Description
Manage your website's Asyntai AI support agent: knowledge base, agent instructions, conversations and leads, live visitor replies and plan usage.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-bridge": {
    "command": "npx",
    "args": ["-y","@asyntai/mcp"],
    "env": {
      "ASYNTAI_MCP_URL": ""
    }
  }
}
```

**Requires environment variables:** `ASYNTAI_MCP_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What asyntai/mcp-bridge MCP server does

asyntai/mcp-bridge MCP server gives a local MCP process access to an Asyntai account. Asyntai provides an AI support agent for websites, and its MCP interface exposes the same 54 tools available in the Asyntai dashboard. Those tools cover adding knowledge, changing agent instructions, reviewing conversations and leads, replying to live visitors, and checking plan usage.

The package is intended for MCP clients that can start a local command but cannot connect to a remote MCP server. Clients with remote MCP support can connect directly to `https://asyntai.com/mcp` instead.

## How it works

The bridge reads MCP JSON-RPC requests from standard input, sends them to the configured hosted server with an authorization header, and writes the responses to standard output. It does not contain a separate implementation of the Asyntai tools or their response formats. As a result, tools added or changed on the hosted server can be available through the bridge without publishing a new package version.

Authentication uses OAuth 2.1 with PKCE. The first tool call opens a browser so the user can approve access; later calls reuse the saved sign-in. No API key is entered. The bridge obtains endpoint information from the server's published metadata rather than relying on fixed internal routes.

## Setup and configuration

Install or run the package through Node.js 18 or newer. A local MCP client can launch it with:

```json
{
  "mcpServers": {
    "asyntai": {
      "command": "npx",
      "args": ["-y", "@asyntai/mcp"]
    }
  }
}
```

The account approval happens in a browser during the first tool call, and the free Asyntai plan is supported. To run it directly, use `npx @asyntai/mcp`. `npx @asyntai/mcp logout` removes the saved credentials, while `npx @asyntai/mcp --help` displays command help.

By default, requests go to `https://asyntai.com/mcp`. Set `ASYNTAI_MCP_URL` to use a different MCP server. Credentials are stored in `~/.asyntai/mcp-credentials.json`; the file contains access and refresh tokens and uses owner-only permissions where supported. Sign-in can also be revoked from Asyntai's connections page.

## Tools and capabilities

The remote Asyntai service supplies 54 tools. Supported work areas include:

- Add and manage website knowledge.
- Edit the support agent's instructions.
- Read conversations.
- Read leads.
- Send replies to live visitors.
- Inspect plan usage.

The bridge passes these capabilities through rather than defining a separate local tool set. It also ships as a Claude Desktop extension in `.mcpb` format, which can be installed from Claude Desktop's Extensions directory or built with the MCPB pack command.

## Limitations and notes

asyntai/mcp-bridge MCP server requires an Asyntai account and an MCP client that can launch a local command. It is not needed when the client supports remote MCP connections to the hosted endpoint. The package requires Node.js 18 or later.

Standard output is reserved for MCP protocol messages; diagnostic output goes to standard error. The bridge stores OAuth tokens locally but does not store other data, send analytics, use third-party services, or add package telemetry. Messages are sent to the Asyntai server selected by the configuration, which processes them under Asyntai's privacy policy.

The package is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/asyntai-mcp-bridge/readme_