# Set up Actually Asked

The person who sent you this link wants Actually Asked on their website. Actually Asked answers visitors' questions from the site's own pages and keeps its FAQ current. Work through the steps below in order, and show the person each change to their site before you make it.

## 1. An Actually Asked account

Ask whether they have one. If not, they sign up at https://actuallyasked.com/users/sign_up (the free plan needs no card) and add their site there. A Shopify store installs the Actually Asked app from the Shopify App Store instead: https://apps.shopify.com/actually-asked

## 2. Connect Actually Asked's MCP server

The server is https://mcp.actuallyasked.com/mcp, over Streamable HTTP with OAuth: connecting opens Actually Asked's sign-in page in the person's browser, where they pick the account.

- Claude Code: run `claude mcp add --transport http --scope user actually-asked https://mcp.actuallyasked.com/mcp`, then ask the person to run `/mcp` and choose Authenticate.
- Codex: run `codex mcp add actually-asked --url https://mcp.actuallyasked.com/mcp`, then `codex mcp login actually-asked`.
- Cursor: ask the person to open cursor://anysphere.cursor-deeplink/mcp/install?config=eyJ1cmwiOiJodHRwczovL21jcC5hY3R1YWxseWFza2VkLmNvbS9tY3AifQ%3D%3D&name=actually-asked or add `{"mcpServers":{"actually-asked":{"url":"https://mcp.actuallyasked.com/mcp"}}}` to `~/.cursor/mcp.json`. Cursor asks them to sign in.
- Claude (claude.ai and the Claude apps): ask the person to add Actually Asked from Claude's connectors directory: https://claude.ai/directory/connectors/actually-asked
- ChatGPT and other assistants: the steps for each are at https://actuallyasked.com/mcp

An assistant usually sees a new server's tools only in a new session. If the Actually Asked tools aren't available to you yet, tell the person what's left to do, and to send this link again once it's connected.

## 3. Put the FAQ on the site

With the Actually Asked tools available, this is the request:

> Set up Actually Asked on my site.
>
> 1. Call list_sites to find the site and what its plan allows.
> 2. Work out what the site is built with (ask me if you can't tell) and call get_install_instructions for that platform.
> 3. If you can edit the site's code, add the widget yourself. On Growth and up, put it once in the layout every page shares, so every page has it and page rules decide what each shows; below Growth, put it where visitors look for answers: product pages, help and contact pages. Make a full FAQ page with the full FAQ container. Where a page is about one product and its address can't pick that out, add data-faq-tag from the template's own data, the product's handle or slug (tags work from the Growth plan). If you can't edit the site, walk me through each step for my platform, one at a time.
> 4. Check it with check_install on a page you changed (for Shopify, check_install reads the live theme), and tell me what you found.
>
> Show me each change before you make it.

## 4. Then

- Review the FAQ entries Actually Asked suggested from the site's pages, and publish the ones the pages back up.
- Each week: what did visitors ask, and what went unanswered? The unanswered ones are what the site's pages are missing.
