EZ-bot

jp.ez-botPublished by ez-bot.jpOfficial publisherv1.0.0Updated Nov 4, 2026

EZ-bot: set up and manage your EZ-bot website AI chatbot (Japan)

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for EZ-bot, a Japanese website AI chatbot service, letting an assistant set up and manage your bot.

What you can do
  • Set up and manage an EZ-bot website AI chatbot.
  • The registry description only states that the server covers chatbot setup and management; no individual tools are listed.
  • No further capability details are published in the supplied material.
When to use it
When you already use the EZ-bot website chatbot service and want an assistant to help configure or manage that bot from a connected client.
Requirements
A remote MCP endpoint at member.ez-bot.jp over streamable HTTP. OAuth authentication is required, so an EZ-bot account with access to the service is needed. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your EZ-bot account, and management actions may change the live chatbot configuration on your website. Review the requested scopes before authorizing, and note that the service is operated by a third party in Japan.

Installation

In SourceWeft

  1. Open EZ-bot in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/jp.ez-bot%2Fezbot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ez-bot": {
      "type": "http",
      "url": "https://member.ez-bot.jp/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.