[ledgr-hostinger]

What changed

Registers hostinger-mail-mcp as a tenth server, hostinger-mail, so an agent using the plugin can manage email.

File	Change
mcp.json	Adds hostinger-mail. Bumps the user-agent strings to 0.3.3.
rules/prefer-mcp-tools.mdc	Adds the mail_ prefix to the server table and a short Email section.
rules/confirm-destructive-actions.mdc	Adds deleting a mailbox, changing its password and creating a Mail API token to the list that needs confirmation.
README.md	Adds the server to the table and mentions email. Removes mail from the "doesn't wire up" sentence.
.cursor-plugin/plugin.json	Version 0.3.3, and email in the description.
CHANGELOG.md	Entry for 0.3.3.

Why

Slack thread: https://hostinger.slack.com/archives/C0218EBLBP1/p1794392140.672959

An agent in Grok with the "Hostinger" plugin installed was asked to create a mailbox and send a test email. It answered that the connection "covers hosting, domains and DNS, but it has no way to create mailboxes" and went looking for a way through hPanel. The earlier report in the Slack thread is the same failure: the agent said the connector is split into parts for hosting, domains, DNS, billing, Reach, VPS and others, and that none of them is for email.

mcp.json registered nine per-product servers from @hostinger/mcp and left hostinger-mail-mcp out. The Grok plugin page shows exactly those nine connectors and the same seven skills, so the plugin Grok installs is built from this repository.

The same task works in ChatGPT and Claude, because their Hostinger Connector listing points at the hosted server, mcp.hostinger.com, which carries every product in one catalog.

Why the rules change too

The mail_ operations only set up email: orders, mailboxes, aliases, forwarders, logs and tokens. They cannot read or send a message. That goes through the Hostinger Mail API at https://api.mail.hostinger.com/, with a token that mail_api-tokens_create issues.

Agents that do not know this ask the user for the mailbox password, or change it. On the hosted server this is covered by an Email section in the instructions sent on connect (hostinger/public-api-generator#306). The per-product mail server does not send that section, so in this plugin the rules file is the only place an agent can learn it.

Related: hostinger/public-api#603 corrected the description of mail_api-tokens_create.

For reviewers

• Was leaving mail out deliberate? The README said the plugin does not wire up the mail server. If there was a reason, it should be weighed against agents telling users that Hostinger has no email tools.
• The version bump is by hand. The nightly mcp-sync workflow also bumps the patch number. If its pull request lands first, 0.3.3 here needs to move to the next free number in plugin.json, mcp.json and CHANGELOG.md.
• Horizons, GPU and agent readiness are also published and not wired up. This change leaves them alone.

Checks

• node scripts/validate-template.mjs: passed.
• node scripts/check-tool-names.mjs: passed, 132 tools referenced and 10 servers mapped to real tool groups.
• The JSON files parse.

Not verified

• The plugin was not run inside Cursor or Grok with this change.
• How soon a merge reaches Grok users is unknown.
• The operation count of 38 in the README row comes from the checked-in catalog for @hostinger/mcp 3.29.0. The next sync may change it.

🤖 Generated with Claude Code