Hostinger AI and MCP: Which Route Reaches Your Posts
Updated October 31, 2026
Hostinger AI comes in three pieces as of October 2026, and only one of them needs a Business or Cloud plan: the MCP endpoint that lets your own Claude or Cursor into WordPress.
The other two are Hostinger Agent, the chat built into hPanel and wp-admin, and an account-level MCP server for domains, DNS and billing. They overlap a little and differ a lot.
| Route | Where you use it | Plan | What it touches |
|---|---|---|---|
| Hostinger Agent | hPanel sidebar, Ask AI button, wp-admin sidebar | Sites on Hostinger WordPress hosting (update the Hostinger plugin first) | Posts, pages, comments, terms, users, settings, WooCommerce products |
| WordPress MCP endpoint | Claude Code, Claude Desktop, Cursor | Business or Cloud, Hostinger AI Plugin | Whatever the site's MCP Adapter exposes |
| Hostinger API MCP | mcp.hostinger.com, OAuth | Any Hostinger account | Websites, VPS, domains, DNS, email marketing, billing |
The Agent can't upload or delete media yet, and it shows a confirmation card before high-impact actions.
The API server's support page says each WordPress site now shows up as its own MCP. It doesn't list which of those per-site tools write anything.
Hostinger Connector support for WordPress is on the roadmap, marked "Planned" as of September 11, 2026.
What Hostinger's WordPress endpoint asks of you
This is the route people mean by "Hostinger MCP," and it's more hands-on than the word "integrated" suggests.
The endpoint lives at yoursite.com/wp-json/mcp/mcp-adapter-default-server, served by the WordPress MCP Adapter that the Hostinger AI Plugin sets up (the adapter explained). Hostinger's guide then has you do three things on your side.
You install Node.js on your own computer, which Hostinger's client config uses to make the connection. You create a WordPress application password under Tools → Hostinger Tools and put it in that config file, so the credential lives on your laptop. And the config sets OAuth off, which is why Hostinger's troubleshooting starts with checking that "Disable application passwords" in Hostinger Tools is switched off.
For Claude Code, the connection is saved in the project's .mcp.json, so it's per folder. Claude Desktop and Cursor each get their own config. That's fine for one developer on one site. It gets fiddly with a team, or with ten client sites that each need their own password.
Which one to use
If you only ever chat inside hPanel, Hostinger Agent is already there and costs nothing extra. If you're on Business or Cloud, comfortable with Node and a config file, and live in Claude Desktop, Claude Code or Cursor, Hostinger's endpoint is a reasonable free start.
Kitepod skips the local setup. You paste one URL into Claude or ChatGPT and sign in with OAuth, so there's no password in a file and nothing to install on your computer. It also works with ChatGPT, which Hostinger's WordPress guide doesn't cover, and it puts sites on other hosts in the same conversation.
It also keeps a history. Ask an AI to rewrite 40 WooCommerce product descriptions and find out two weeks later it invented a "machine washable" claim on half of them: through Kitepod, those 40 edits were one change set, and one undo takes them all back. Content edits under the default policy run straight away, while database (SQL) writes, user changes and plugin installs wait for you. The rest is on the WordPress MCP page.
Installing Kitepod from hPanel
Kitepod is a free MCP server and plugin. It doesn't run a model, so the thinking happens on your own Claude or ChatGPT plan, and it only needs your server to make outgoing HTTPS calls.
- In hPanel, open Websites → Websites list and press WP Admin beside the site. Upload the Kitepod zip under Plugins → Add New → Upload and activate it (the site needs WordPress 6.4 or later, PHP 7.4 or later).
- Press Connect on the Kitepod screen in wp-admin and choose the WordPress user whose permissions the AI borrows.
- Paste
https://kitepod.com/mcpinto Claude's custom connector dialog or ChatGPT's plugin screen (ChatGPT steps) and approve the sign-in.
We haven't tested Kitepod alongside the Hostinger AI Plugin's endpoint. On paper they don't collide, but they keep separate histories, and Kitepod can only undo what went through Kitepod.
LiteSpeed, the CDN and OpCache
Hostinger splits caching across three screens, which explains most "the change didn't save" moments.
Cache Manager (open the site from Websites, then search the dashboard for it) purges only the LiteSpeed server cache. The Hostinger CDN is purged in its own CDN section. PHP OpCache sits under PHP Configuration. Hostinger also asks you to keep to one cache plugin per site.
If an edit doesn't show to visitors, purge in Cache Manager first, then the CDN.
Finer points
Does Hostinger have an MCP server?
Two kinds. mcp.hostinger.com works on your account (domains, DNS, VPS, billing and more), and the Hostinger AI Plugin adds a WordPress endpoint on Business and Cloud sites.
Is Hostinger Agent the same as the WordPress MCP endpoint?
No. The Agent is Hostinger's own chat. The endpoint is a door for your own assistant, and it needs Business or Cloud.
Does Kitepod work on Hostinger Website Builder sites?
No. Those aren't WordPress, and Kitepod needs a self-hosted WordPress site that can run plugins.
Can I use ChatGPT on a Hostinger WordPress site?
Hostinger's WordPress MCP guide covers Claude Code, Claude Desktop and Cursor. ChatGPT works through Kitepod's remote server with an OAuth sign-in, on any Hostinger plan that runs WordPress plugins.