protogrid

Search / ai.theautomators/mcp

The Automators

R0· no sign-in

Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators.

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust83of 100
Uptime, 30 days100%
Latency p50273 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "theautomators": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
claude mcp add --transport http theautomators https://mcp.theautomators.ai/mcp
[mcp_servers.theautomators]
url = "https://mcp.theautomators.ai/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theautomators": {
      "type": "remote",
      "url": "https://mcp.theautomators.ai/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "theautomators": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=theautomators&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnRoZWF1dG9tYXRvcnMuYWkvbWNwIn0%3D"
}
{
  "servers": {
    "theautomators": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
{
  "mcpServers": {
    "theautomators": {
      "httpUrl": "https://mcp.theautomators.ai/mcp"
    }
  }
}
extensions:
  "theautomators":
    enabled: true
    name: "theautomators"
    type: streamable_http
    uri: "https://mcp.theautomators.ai/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_company_profile (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_contact_options (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_engagement_process (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 2,881 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

18 tools, about 2,881 tokens to load them all · tool set 2462a87e92f6 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository
provenance55
liveness100
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-30d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp.theautomators.ai/mcp streamable-httpnoneyes100%273 ms2025-11-252026-10-19

Tools (18)

assess_ai_readinessRuns 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, Advanced), the percent score, the per-dimension breakdown, the weakest dimensions and service recommendations.
check_service_areaResolves 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 whenever a user mentions where they are.
estimate_customer_service_savingsRuns 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 deflected, response-time reduction and ROI, with service recommendations. Use it for support-desk cost questions. An industry preset fills typical inputs.
estimate_roiRuns 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 shows. Use it when a user wants a number for the value of automating a process. Optional industry preset sets the automation efficiency.
get_blog_postReturns 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/.
get_case_studyReturns one real case study in full: facts, metrics and the page narrative as markdown. Get the slug from list_case_studies.
get_company_profileReturns 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 introduce the company or check a fact about it. It is not the place for pricing (get_pricing) or contact details (get_contact_options).
get_contact_optionsReturns 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 whenever the user wants to talk to a human or book a consultation. The server never sends messages; it only returns these options.
get_engagement_processReturns 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 for "how does working with you go" questions.
get_faqReturns 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 question in the site's own words.
get_industry_playbookReturns 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), compliance notes, FAQs and related industries. Use it when the user names an industry.
get_pricingReturns 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, budget or "how much" question. Figures come from the same module the site renders, so quote them as given.
get_serviceReturns 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 whether it fits their need. Get the slug from list_services.
list_case_studiesReturns 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_industriesReturns 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_servicesReturns 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_processesRuns 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 implementation timeline, ranked, plus totals and service recommendations. Use it when a user lists several things they might automate.
search_contentKeyword 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_post, get_service or get_industry_playbook.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "ai.theautomators/mcp",
  "title": "The Automators",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.theautomators.ai/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://theautomators.ai/mcp/",
  "description": "Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators."
}