@asyntai/mcp
Official@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 --helpHow 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 |
| Point at a different server. Defaults to |
Diagnostics go to stderr. stdout carries the protocol and nothing else.
Development
npm testNo 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 packPrivacy 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
MIT.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/asyntai/mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server