The Automators is an MCP server with 18 tools an agent can call, among them assess_ai_readiness, check_service_area, estimate_customer_service_savings. It answers at https://mcp.theautomators.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, succeeded.
Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
assess_ai_readiness | Runs the site's AI Readiness Assessment. Call it with no answers to get the 10 questions and their scored options; ask the user; then call it again with one score (1 to 4) per question in order to get the level (Beginner, Intermediate, Adva Inputs: answers |
check_service_area | Resolves a city, province, state or country to the matching local page (649 Canadian and US pages) and says whether it is served. Anything outside Canada and the US is served remotely and resolves to the locations index with a note. Use it Inputs: query |
estimate_customer_service_savings | Runs the site's Customer Service Cost Calculator: from monthly tickets, handle time, agent cost, agents on staff, response time and after-hours share it estimates current and AI-assisted monthly cost, monthly and annual savings, tickets def Inputs: monthlyTickets, avgHandleTime, agentHourlyCost, agentsOnStaff, avgResponseTime, afterHoursPercent |
estimate_roi | Runs the site's ROI calculator: from team size, weekly manual hours, hourly cost and error rate it estimates annual hours saved, annual savings, implementation cost, ROI percent and payback months, plus the service recommendations the page Inputs: employees, hoursPerWeek, hourlyCost, errorRate, industry, automationEfficiency |
get_blog_post | Returns one blog post as markdown: title, author, date, the full body with links, a Sources list and the post's FAQs. Use search_content to find the slug. Every post is written by The Automators' team and published at theautomators.ai/blog/ Inputs: slug |
get_case_study | Returns one real case study in full: facts, metrics and the page narrative as markdown. Get the slug from list_case_studies. Inputs: slug |
get_company_profile | Returns who The Automators are: name, description, founding year, headquarters, service area, the public team (name, role, LinkedIn, bio), verified public profiles, the content licence (RSL 1.0) and headline track record. Use it to introduc |
get_contact_options | Returns how a person reaches The Automators: phone, the public email, the booking page and direct calendar link, business hours, the response-time promise, and what to include in an inquiry (company, what to automate, timeline). Use it when |
get_engagement_process | Returns the four engagement steps (discover and map, opportunity analysis, build and integrate, optimise and scale) with what happens in each, what the client provides, the typical timeline and how it starts (a free consultation). Use it fo |
get_faq | Returns the site FAQs for a topic: "general" (the homepage questions), "pricing" (the /pricing/ questions), or a service, industry or tool slug (that page's questions). Omit the topic for general plus pricing. Use it to answer a common ques Inputs: topic |
get_industry_playbook | Returns the playbook for one industry: a TL;DR, the industry landscape with verified, cited statistics, the workflows we automate (pain point, automation, outcome), relevant services, illustrative example use cases (not client work), compli Inputs: slug |
get_pricing | Returns the pricing model: one-time build price, ongoing model costs paid to the provider, ownership, no retainer, typical timeline and ROI window, what is included, what is billed separately, and who it is not for. Use it for any cost, bud |
get_service | Returns everything the site says about one service: description, the full page text as markdown, its FAQs, related real case studies, and the pricing and timeline that apply. Use it when a user asks what a specific service involves or wheth Inputs: slug |
list_case_studies | Returns the four real, published case studies with client, industry, summary, owner-confirmed metrics and URL. These are the only pages that describe The Automators' own past work. Use get_case_study for the full story. |
list_industries | Returns the 20 industries with a dedicated playbook page: slug, name, audience, one-line description and URL. Use it to find the slug for get_industry_playbook. |
list_services | Returns the six service pillars and the eleven AI Agent Development capabilities, each with a one-line description and URL. Use it first to find the right service slug before calling get_service. Not for pricing (get_pricing). |
prioritize_processes | Runs the site's Process Prioritizer on up to 10 manual processes (name, hours per week, frequency, complexity, error-prone, people involved). Returns each one's score out of 100, priority, estimated annual savings, reasoning and implementat Inputs: processes |
search_content | Keyword search across blog posts, services, industries, tools and case studies. Returns ranked results with type, title, URL, description, date and TL;DR where available. Use it to find the right page or post before reading it with get_blog Inputs: query, limit |
Every block below points at https://mcp.theautomators.ai/mcp. Pick your client and copy.
claude mcp add --transport http the-automators https://mcp.theautomators.ai/mcp
{
"mcpServers": {
"the-automators": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.theautomators.ai/mcp"]
}
}
}{
"mcpServers": {
"the-automators": {
"url": "https://mcp.theautomators.ai/mcp"
}
}
}{
"servers": {
"the-automators": {
"type": "http",
"url": "https://mcp.theautomators.ai/mcp"
}
}
}{
"context_servers": {
"the-automators": {
"url": "https://mcp.theautomators.ai/mcp"
}
}
}{
"mcpServers": {
"the-automators": {
"serverUrl": "https://mcp.theautomators.ai/mcp"
}
}
}{
"mcpServers": {
"the-automators": {
"url": "https://mcp.theautomators.ai/mcp"
}
}
}name: The Automators
version: 0.0.1
schema: v1
mcpServers:
- name: The Automators
type: streamable-http
url: https://mcp.theautomators.ai/mcp{
"mcpServers": {
"the-automators": {
"httpUrl": "https://mcp.theautomators.ai/mcp"
}
}
}{
"mcpServers": {
"the-automators": {
"type": "http",
"url": "https://mcp.theautomators.ai/mcp"
}
}
}{
"mcpServers": {
"the-automators": {
"url": "https://mcp.theautomators.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.theautomators.ai%2Fmcp&type=streamable_http&id=the-automators&name=The%20Automators
It answered our last check on 6 November 2026 in 239 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by theautomators.ai and served from mcp.theautomators.ai, the vendor's own domain: https://mcp.theautomators.ai/mcp.
18, as returned by the server's own tools/list on 11 November 2026: assess_ai_readiness, check_service_area, estimate_customer_service_savings, estimate_roi, get_blog_post, get_case_study, get_company_profile, get_contact_options, and 10 more.
It answered our last check on 6 November 2026 in 239 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.theautomators.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.theautomators. Endpoint host: mcp.theautomators.ai. ARD identifier: urn:air:ai.theautomators:mcp:mcp.
First indexed 19 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.