answerhatch-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANSWERHATCH_TOKEN | No | Optional bearer token for AnswerHatch API authentication. If set, the answerhatch_login tool can be skipped. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| answerhatch_loginA | Sign in and hold the bearer token for the rest of this session. Call this once before any other answerhatch tool. Skip it when the server was started with ANSWERHATCH_TOKEN set. This tool does not create accounts: sign up first at answerhatch.com/signup. Never print the password back to the user. |
| answerhatch_create_tenantA | Register one domain and return its tenant id plus the DNS TXT record that proves the customer controls it. The crawl does not start here. Give the record to the user verbatim, wait for them to publish it, then call answerhatch_start_crawl. Call this once per site; if a crawl will not start, retry the crawl rather than registering again. |
| answerhatch_start_crawlA | Start the crawl for a registered tenant. Call it only after the TXT record from answerhatch_create_tenant is published. If the record is not visible yet the tool returns the record again with instructions to publish and retry: wait about a minute and call this tool again. The crawl is asynchronous, so poll answerhatch_status afterwards. |
| answerhatch_statusA | Report a tenant's lifecycle stage, worker phase, pages crawled and domain verification. Poll this every 20 to 30 seconds while a crawl runs. When the stage reaches live it also returns the embed snippet and the steps for pasting it into the site, which is the end of onboarding. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: authentication, domain registration, crawl initiation, and status polling. There is no overlap or ambiguity between them.
All tools follow a consistent 'answerhatch_<verb/noun>' pattern with lowercase snake_case, making the naming uniform and predictable.
With exactly 4 tools, the set is concise and well-scoped for the onboarding workflow it implements, fitting comfortably within the ideal range.
The tools cover the full lifecycle from authentication through domain verification, crawl execution, and final status reporting with embed snippet delivery. No essential operations are missing for the stated purpose.