MCP Bridge
Manage your website's Asyntai AI support agent: knowledge base, agent instructions, conversations and leads, live visitor replies and plan usage.
Installation
Les étapes d'installation sont dans la documentation ci-dessous. Documentation
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
@asyntai/mcp
Connect any MCP client to your Asyntai account.
Asyntai puts an AI support agent on your website that answers visitors from your own content. This package gives your assistant the same 54 tools the Asyntai dashboard has: add knowledge, edit the agent's instructions, read conversations and leads, and reply to a live visitor yourself.
Do you need this?
Probably not, and that is deliberate.
Asyntai runs a hosted MCP server at https://asyntai.com/mcp. If your client
supports remote MCP servers, which Claude, ChatGPT, Cursor and VS Code all do,
add that URL directly and skip this package.
This is for clients that can only launch a local command. It bridges one to the other and handles the sign-in.
Use it
{
"mcpServers": {
"asyntai": {
"command": "npx",
"args": ["-y", "@asyntai/mcp"]
}
}
}
The first tool call opens a browser once so you can approve access. After that it is silent. You need an Asyntai account; the free plan works.
Commands
npx @asyntai/mcp # run the bridge
npx @asyntai/mcp logout # forget the saved sign-in
npx @asyntai/mcp --help
How it works
It is a transparent proxy. It reads JSON-RPC messages on stdin, posts them to
the hosted server with an Authorization header, and writes the replies to
stdout. It does not know what the tools are or what they return, which is why
new tools on the server work here without a new release.
Sign-in is OAuth 2.1 with PKCE, the same flow Claude and ChatGPT use. No API key is ever entered. The endpoints are read from the server's published metadata rather than hard-coded, so a route change on the server does not break this package.
Where the sign-in is kept
~/.asyntai/mcp-credentials.json, with owner-only permissions where the
operating system supports them. It holds an access token and a refresh token
for each server you connect to. logout removes them.
Revoking from the Asyntai side is at asyntai.com/mcp/connections, which kills the tokens immediately whatever is on disk.
Options
| Variable | Meaning |
|---|---|
ASYNTAI_MCP_URL | Point at a different server. Defaults to https://asyntai.com/mcp. |
Diagnostics go to stderr. stdout carries the protocol and nothing else.
Development
npm test
No dependencies, and none planned. Node 18 or newer.
Claude Desktop extension
The same bridge ships as a Claude Desktop extension (.mcpb). Install it from
the Extensions directory in Claude Desktop, or build it yourself:
npx @anthropic-ai/mcpb pack
Privacy Policy
This bridge stores nothing except the OAuth tokens described above, on your
own machine. Every message goes only to the Asyntai server you connected to
(by default https://asyntai.com/mcp), which processes it under the
Asyntai privacy policy. No analytics,
no third-party services, no telemetry from this package.
Links
- Connector documentation
- Privacy policy
- hello@asyntai.com
MIT.
Questions fréquentes
Qu'est-ce que MCP Bridge ?
Manage your website's Asyntai AI support agent: knowledge base, agent instructions, conversations and leads, live visitor replies and plan usage.
Comment installer MCP Bridge ?
Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.
MCP Bridge est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient MCP Bridge ?
Il est publié par asyntai. AI.tn le référence sans le maintenir ni le recommander.
Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.