Skip to content
EnterraHost
Client Area Find a domain
Products
Build a bundle Domain Names Shared Web Hosting Business Email Mail Protection EnterraMon EnterraSEO EnterraEdit
Tools
SPF, DKIM and DMARC Checker Ping Test Traceroute Server Check IPv6 Test DNS Lookup MAC Address Lookup Robots.txt Tester Broken Link Checker Link Visualiser Sitemap Validator Website Audit
Hosting Email Support Client Area Find a domain

Connect your own agent to your EnterraHost data

By EnterraHost Network Operations Team Published

Your EnterraMon and EnterraSEO data can be read by the agent you already use, through a read-only MCP key. The agent reads the measurements. It does not get file, database, SSH or control-panel access from that key.

This is done in the toolbox. Sign in at toolbox.enterrahost.com and open Account settings from the navigation, then Agent access. The section appears only when an EnterraMon or EnterraSEO product is active on your account.

What you need

  • An active EnterraMon or EnterraSEO product.
  • An MCP-capable agent that supports a remote MCP server over Streamable HTTP, or a local bridge that can reach one.
  • The MCP endpoint. EnterraMon uses https://mcp.enterrahost.com/enterramon/mcp and EnterraSEO uses https://mcp.enterrahost.com/enterraseo/mcp. The endpoint is not your website address.
  • A backup and a rollback plan if the agent will do more than read.

Create the key

In Agent access, choose Create agent key, give it a name you will recognise, and copy it once. The key is not shown again. Store it in the agent's secret or environment store rather than in a prompt, a document or a ticket.

The key list shows the product access it carries. If a product is canceled, that access stops on the next check. The key is not a permanent grant.

The Create an agent key dialog in the EnterraHost toolbox. A robot icon sits beside the title, and the text reads that the key will have the access shown above, is read-only and scoped to the account, and asks for a name so it can be recognised later. The Name field is empty with a placeholder of e.g. My DeepSeek agent. Below it, a note says the key is shown once on the next step, cannot be revealed again, and should be revoked and replaced if lost. Cancel and Create key buttons sit at the bottom right.
The name is a label for your own list. It grants nothing.
The same dialog after creating a key, headed Copy this key now, it will not be shown again. A text field holds a key beginning ent_live_txz followed by masked dots and ending 0uZc, with a Copy button beside it. Under the field, Access is listed as EnterraMon and EnterraSEO, and an I have copied it button closes the dialog.
This is the only time the value exists on screen. Copy it into the agent's secret store, not into a prompt.

Connect the agent

Every MCP client asks for the same three things, a server URL, a transport and an authorization header. Add the endpoint above and the key to the client's MCP or connector settings, then ask the agent to list its EnterraHost tools.

A 401 means the key is wrong, revoked or missing from the header. A 403 means the key is valid but that product is not active. No tools at all usually means the endpoint or transport is wrong.

The full setup guide has a copy-paste agent brief, the tool sequence, and the platform notes for WordPress, Joomla, PHP and ASP.NET. It is at enterrahost.com/agent-access, and the Markdown version is there for the agent to read directly.

Check freshness before acting

All timestamps are UTC. The newest audit or crawl is a point-in-time snapshot. Older rows are history for trends, not current state.

EnterraMon labels each audit as scheduled or on-demand. Multiple on-demand tests can share one date, so the audit history is a list rather than one row per day.

If the latest audit is on-demand, stale, or older than the expected cadence, the agent must tell you what is unscheduled or stale, explain that the findings may no longer describe the site, and obtain your explicit permission before acting on them. The MCP cannot trigger a new crawl or audit.

If you give it site access

The MCP key is separate from any site credential. Giving the agent access to the actual site is a second decision, and it is the one that can break something. Start read-only, then staging, then production only with a backup, a Git branch or tag, staging verification and human approval.

Use a separate least-privilege account. Do not give an agent root SSH, DNS, payment or authentication access for a content fix. Do not put site credentials in a prompt. Take a database and file backup, prove the restore path, and keep the rollback available until verification passes.

Start with titles, meta descriptions, alt text, schema, canonical, robots.txt and llms.txt. Do not start with theme or plugin code, plugin updates, DNS changes or bulk deletions.

The agent access guide covers the full change loop and the stop conditions. Read it before the first production change.

Summarize this guide with

Claude ChatGPT DeepSeek

You need an account with the assistant you choose. It fetches the guide itself, and you send the prompt, not us.

Every guide in this category is on the Agent access page.

Something here wrong, or out of date? Tell us at editorial@enterrahost.com.