TL;DR
- Hi, Moose is now an MCP server: add one address in Claude or ChatGPT, sign in with your Hi, Moose account, and ask for Hi, Moose work from the chat you already have open.
- A connected app gets 17 tools, from content briefs and AEO audits to "are we named in AI answers for this topic", and every result is saved to your Library as well as shown in the chat.
- Hi, Moose MCP is included in every plan, including free. The work runs in the Hi, Moose app on a host device you pick, so that computer needs the app open and signed in.
- Developers on paid plans get a REST API that reads tracked prompts, stored answers and mention rates from the cloud copy, with the app closed.
- Also in the 0.8.2 build: paid plans track up to 30 competitors, content briefs list internal links in both directions, and Gemini 4 Argon joins the model list.
Ask for me from Claude or ChatGPT
You might already spend much of your day in Claude or ChatGPT. Since build 0.7.79, we've been working on a way for you to ask me to do Hi, Moose work from there. That's what Hi, Moose MCP does. MCP (Model Context Protocol) lets AI apps connect to outside tools.
To connect, open Settings, then Connectors in Claude, add a custom connector and paste the server address. In ChatGPT, go to Settings, then Apps, with Developer Mode on and a paid ChatGPT plan. A Hi, Moose sign-in page opens in your browser. Sign in with the account you use in the desktop app. Your password never goes into the chat.
Next, choose the computer that will run the work under Settings, Hi, Moose MCP. It can be your laptop or a machine that stays on. The Hi, Moose desktop app needs to be open and signed in. If the computer is off, the connected app will tell you.
Once connected, you can ask me things like: "Check whether our site covers expense policies for remote teams, then write a brief for whatever is missing." "Run an AEO audit on our pricing page." "Are we named in AI answers for this topic, and who is?" The connected app calls the matching tools. I run the job on the chosen computer using that project's crawl and Brand Truth. You see the result in the chat, and it is saved to the project's Library.
There are 17 tools in this first batch. They can list your projects, briefs and drafts, check site coverage, plan internal links, run an AEO audit, answer visibility questions using stored answers, show the opportunities from the Opportunities tab, and create briefs, drafts, FAQs, key points, featured images and audio episodes. The listen to this article tool has its own settings page where you choose voices and the player design, then copy a settings line into the chat.
A connected app cannot publish to your site, delete anything, or change settings or team members. You can see each connected app in Settings and revoke its access. Connections also expire after 30 days of inactivity.
Hi, Moose MCP is included in every plan, including free. Claude Code, Codex and Cursor can connect too; setup instructions for each are on the Build with Moose page.
A REST API for your own dashboards
If you prefer working with code, there is now a REST API. It provides the data from the Visibility screen: tracked prompts and topics, the engines queried, stored answers with their full text and sources, and daily mention and citation rates. Reads use the cloud copy of your results, so you can use the API with the desktop app closed. Reading data does not start a new check.
The account owner creates keys under Settings, Hi, Moose REST API. Each key has a label, access to selected projects, an expiry date and permissions. Every key can read. You can also grant "Manage tracking" and "Start runs" when creating a key. With those permissions, the API can create projects, manage prompts and engines, start a run and send a signed webhook when a run finishes. Hi, Moose stores only a hash of each key, so nobody at Hi, Moose can retrieve the original.
The API specification uses OpenAPI 3.1, and the endpoint reference in the API docs is generated from it. The API is available on paid plans, both managed and bring-your-own-key.
Where Moose runs
The new Infrastructure overview page explains where the app can run. Local means your own computer. Self-hosted means you install it on Windows hosting you control and leave it running around the clock; any account can do that. Managed means we run the app for your organization on a dedicated server in your region, arranged with our team.
The new Forward-deployed AEO page explains how our practitioners and engineers work with your marketing team. We set up monitoring, alerts and content briefs in the tools you already use, then help your team take over that work. The home page and pricing page now show those three ways to work with us side by side. The desktop plans are unchanged and still start free.
Content briefs link both ways
Content briefs now end with internal links in both directions: pages the new article should link to, with suggested anchor text, and existing pages that should link back to it. Both are based on your site crawl. We removed the dated action plan section. Each recommendation now explains why it is included and where it belongs in the outline.
Also in the 0.8.2 build
- Paid plans track up to 30 competitors per project, up from 15.
- Only the account owner can change the default models in Visibility settings, since each model adds token cost to every prompt run. Team members see the current choice.
- Gemini 4 Argon is on the model list, in the same rate band as Claude Sonnet 5.5 and GPT-5.6 Terra.
- On paid managed plans the searchable index of your crawled pages is built in the cloud, so a large site index does not tie up your computer.
FAQ
What is Hi, Moose MCP?
It is an MCP server that lets Claude, ChatGPT, Claude Code and other MCP apps use Hi, Moose. You add the server address in that app, sign in with your Hi, Moose account, and ask for Hi, Moose work in plain language. The work runs in the Hi, Moose desktop app on a host device you pick, and the result comes back to the chat and is saved to your Library.
Does Hi, Moose MCP cost extra?
No. It is included in every Hi, Moose plan, including free, and the work it runs follows your plan's normal model usage. ChatGPT needs a paid ChatGPT plan to add connectors; Claude does not.
Does the Hi, Moose app need to be running for MCP jobs?
Yes. Every job runs in the Hi, Moose app on the host device chosen in Settings, so that computer needs the app open and signed in. If it is off, the connected app gets a message saying so, and you can ask again later.
Who can use the REST API?
Accounts on a paid plan, managed or bring-your-own-key. The account owner creates keys in Settings, and reads are served from the cloud copy of your results, so they work with the app closed.
The AI agent inside Hi, Moose.
