Hooky

com.heyhookyPublished by heyhooky.comOfficial publisherv1.1.0Updated Nov 6, 2026

Live chat and AI agent for websites: answer visitors, manage sites, the AI agent and stats.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hooky is a remote MCP server for live chat and an AI agent on websites, letting an assistant answer visitors and manage sites, the agent and stats.

What you can do
  • Answer website visitors through live chat and the AI agent.
  • Manage the connected websites and the AI agent's configuration.
  • Review chat and agent statistics.
  • Tool-level detail is not published in the registry entry, so the exact actions available are only visible after connecting.
When to use it
Useful when you run websites with Hooky chat and want an assistant to handle visitor conversations, adjust the AI agent or check performance figures without opening the dashboard.
Requirements
A remote endpoint at api.heyhooky.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared. A Hooky account with at least one connected website is implied.
Before you install
OAuth grants the assistant access to your Hooky workspace, which includes live customer conversations and site settings. Actions may reply to visitors or change the AI agent's behavior, so review what it does before enabling it on production sites.

Installation

In SourceWeft

  1. Open Hooky 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/com.heyhooky%2Fhooky/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": {
    "hooky": {
      "type": "http",
      "url": "https://api.heyhooky.com/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

2
  1. v1.1.0LatestNov 6, 2026
  2. v1.0.0Oct 15, 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.