What is the difference between using this backend and private key mode?
This backend uses zkLogin for authentication and a dashboard for manual transaction approval. Private key mode, detailed in the main repo, allows use without the backend.
@tamago-labs
Basic information
Serverless-based MCP server implementation for Sui blockchain using zkLogin
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This server implements the backend infrastructure for enabling Model Context Protocol (MCP) services on the Sui blockchain using zkLogin. It is part of the Sui Butler system and is built with the AWS Serverless Stack, providing APIs, databases, and a user dashboard for managing access keys and approving transactions. It is designed for developers building AI‑powered tools that interact with the Sui blockchain while leveraging zkLogin authentication.
Deploy the full‑stack application to AWS using the AWS Amplify infrastructure code. After deployment, users authenticate via zkLogin (only Google accounts supported in this version) to access the dashboard. Transaction requests from an MCP‑compatible AI client are stored in the database with a pending status; the user then visits the dashboard to manually approve them. Alternatively, the private key mode (documented in the main repo) can be used without this backend.
This backend uses zkLogin for authentication and a dashboard for manual transaction approval. Private key mode, detailed in the main repo, allows use without the backend.
It relies on AWS Amplify (serverless stack), Next.js for the frontend and API routes, Enoki for zkLogin, and a database for metadata storage.
Metadata associated with zkLogin accounts – specifically each user’s email and wallet address – is stored in the database.
The zkLogin authentication currently supports only Google accounts.
Users authenticate via zkLogin through Enoki. Transaction requests are pushed from an MCP‑compatible AI client to the backend, stored as pending, and then approved manually on the dashboard.
A docker MCP Server (modelcontextprotocol)
The official MCP server for Muumuu Domain by GMO Pepabo, Inc — the first remote MCP server in the Japanese domain registrar industry. Search and register domains, manage owned domains and contracts, and configure DNS rec

Build and run websites, APIs, automations, and admin tools from chat. Your agent creates the data, logic, pages, and scheduled jobs; Tessryx hosts them on your own domain. No code generated, nothing to deploy.

HostTracker is a website and infrastructure monitoring service that has run external checks since 2004 for more than 500,000 websites. Its official MCP server lets an AI assistant operate a HostTracker account directly i
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
Comments