MCP server for DeepL translation API
Nothing to run from here
The Automators is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http the-automators-mcp https://mcp.theautomators.ai/mcp
# 2 — ask your agent for something these tools do
# get_company_profile, get_contact_options, get_faq and 15 more
The Automators costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
theautomators1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http the-automators-mcp https://mcp.theautomators.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 introduce the company or check a fact about it. It is not the place for pricing (get_pricing) or contact details (get_contact_options).
No parameter schema on file.
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 whenever the user wants to talk to a human or book a consultation. The server never sends messages; it only returns these options.
No parameter schema on file.
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 question in the site's own words.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | "general", "pricing", or a service/industry/tool slug such as "ai-voice-communication" or "healthcare" |
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).
No parameter schema on file.
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 whether it fits their need. Get the slug from list_services.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Service slug, e.g. "ai-voice-communication" |
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, budget or "how much" question. Figures come from the same module the site renders, so quote them as given.
No parameter schema on file.
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 for "how does working with you go" questions.
No parameter schema on file.
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.
No parameter schema on file.
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), compliance notes, FAQs and related industries. Use it when the user names an industry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Industry slug, e.g. "healthcare" |
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.
No parameter schema on file.
Returns one real case study in full: facts, metrics and the page narrative as markdown. Get the slug from list_case_studies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Case study slug, e.g. "scada-system-automation" |
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Post slug from search_content, e.g. "legal-workflow-automation-a-practical-guide-for-modern-teams" |
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 whenever a user mentions where they are.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A place, e.g. "Calgary", "Portsmouth, VA", "Ontario", "Berlin" |
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_post, get_service or get_industry_playbook.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords, e.g. "voice agent" or "invoice processing" |
| limit | integer | no | Maximum results (1 to 20) |
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 shows. Use it when a user wants a number for the value of automating a process. Optional industry preset sets the automation efficiency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employees | integer | no | People doing the manual work (1 to 100) |
| hoursPerWeek | integer | no | Hours per person per week on manual tasks (1 to 40) |
| hourlyCost | integer | no | Fully loaded hourly cost per person, CAD (15 to 150) |
| errorRate | number | no | Percent of manual work containing errors (0 to 25) |
| industry | string | no | Optional preset; fills any input left out and sets automationEfficiency unless given explicitly |
| automationEfficiency | number | no | Share of manual hours automation removes (default 0.70; presets use 0.60 to 0.75) |
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, Advanced), the percent score, the per-dimension breakdown, the weakest dimensions and service recommendations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | array | no | One score from 1 to 4 per question, in question order (10 questions). Omit to receive the questions. |
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 implementation timeline, ranked, plus totals and service recommendations. Use it when a user lists several things they might automate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| processes | array | yes | — |
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 deflected, response-time reduction and ROI, with service recommendations. Use it for support-desk cost questions. An industry preset fills typical inputs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monthlyTickets | integer | no | Support tickets per month (100 to 50000) |
| avgHandleTime | integer | no | Average handle time in minutes (2 to 30) |
| agentHourlyCost | integer | no | Agent hourly cost, CAD (15 to 75) |
| agentsOnStaff | integer | no | Agents on staff (1 to 50) |
| avgResponseTime | integer | no | Average first response time in minutes (1 to 120) |
| afterHoursPercent | integer | no | Percent of tickets arriving after hours (0 to 60) |
| industry | string | no | Optional preset; fills any input left out |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install The Automators or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish The Automators can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.