Wakato

io.wakatoPublished by wakato.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Your Wakato account: contacts, tables, pages, email, social, shop, automations and agents.

Overview

AI-generated overview

Remote Wakato MCP server that lets an assistant work with a Wakato account's contacts, tables, pages, email, social, shop, automations and agents.

What you can do
  • Manage contacts and tables in the Wakato account
  • Work with pages and site content
  • Handle email and social channels
  • Access shop data
  • Set up or run automations and agents
When to use it
Useful if your team already runs on Wakato and you want an assistant to read and act on that account's contacts, content, email, shop and automations without switching tools.
Requirements
A remote MCP endpoint at mcp.wakato.io reached over streamable HTTP, with OAuth sign-in to a Wakato account required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the assistant access to a whole business account covering contacts, email, social, shop and automations, so scope and revoke the connection carefully. The tool list is not published, so what it can write, send or delete is unclear; assume it may change account data.

Installation

In SourceWeft

  1. Open Wakato 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/io.wakato%2Fwakato/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": {
    "wakato": {
      "type": "http",
      "url": "https://mcp.wakato.io/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.0LatestOct 13, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.

Other Wakato integrations