MCP Automations MCP server
online · 100% uptimeio.github.wzltmp/mcp-automations·v0.1.0Summarize URLs, repurpose content, daily news digests, find competitors. Cost telemetry built in.
0 stars
Reviews
Write oneNobody has reviewed MCP Automations yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MCP Automations tools (4)
write = sends, deletes, buys or postsdaily_digestFreeSearch the web for recent news on ``topic`` and return a digest with citations.
find_competitorsFreeIdentify ``n`` plausible competitors for a company at ``domain`` (e.g., 'stripe.com').
repurpose_contentFreeRepurpose long-form text into ``twitter_thread``, ``linkedin_post``, or ``newsletter``.
summarize_urlFreeFetch a URL, extract clean article text, and return an N-bullet summary.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 621ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 85 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How MCP Automations compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 84/100
- higher than 68% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 436 ms
- faster than 34% of 30,031 servers
What its tools let an agent do: 4 read
Install MCP Automations in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp-automations https://mcp-automations.fly.dev/mcp
What the publisher says
From the MCP Automations repository's README, as published. We do not edit it. Read it on GitHub
MCP Automations
A production-grade Model Context Protocol server in Python — four LLM-callable tools, two transports, deployed two different ways.
# 30-second proof the server is up:
curl -X POST https://mcp-automations.fly.dev/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","method":"initialize","id":1,
"params":{"protocolVersion":"2024-11-05",
"capabilities":{},
"clientInfo":{"name":"curl","version":"1"}}}'What this is
Most "AI engineer" portfolio projects are applications (a RAG chatbot, an agent that does research). This project is the layer underneath — the typed tools an LLM can call and the transport plumbing that exposes them. MCP is the emerging standard for LLM tool use (~97M monthly SDK downloads as of early 2026); building one — not just consuming one — is the rare skill.
For a deeper look at the design decisions — why two transports, how cost telemetry works, the exception hierarchy, what I'd do differently — see WRITEUP.md.
Tools
Plus one MCP resource (automations://catalog) and one MCP prompt (daily_brief) — using all three MCP primitives, not just tools.
Every tool returns a typed Pydantic model with per-call token usage and dollar cost attached. Cheap tasks route to Haiku 4.5 ($1/M in, $5/M out), writing-heavy tasks to Sonnet 4.6 ($3/M in, $15/M out).
Connect Claude Desktop to this server
Add one of these to ~/Library/Application Support/Claude/claudedesktopconfig.json (Mac) or %APPDATA%/Claude/claudedesktopconfig.json (Windows), then restart Claude Desktop.
Option A — local stdio (no network, runs the server as a subprocess):
{
"mcpServers": {
"mcp-automations": {
"command": "python",
"args": ["-m", "mcp_server.server"],
"cwd": "/absolute/path/to/mcp-automations",
"env": {
"ANTHROPIC_API_KEY": "sk-ant-...",
"TAVILY_API_KEY": "tvly-..."
}
}
}
}Option B — remote HTTP (talks to the live Fly server, no local setup):
{
"mcpServers": {
"mcp-automations": {
"url": "https://mcp-automations.fly.dev/mcp",
"transport": "http"
}
}
}Then ask Claude something like "summarize https://www.paulgraham.com/greatwork.html in 3 bullets" — it'll call summarize_url automatically.
Run locally
pip install -r requirements.txt
# Stdio (for Claude Desktop):
python -m mcp_server.server
# HTTP server (defaults to 0.0.0.0:8765):
MCP_TRANSPORT=http python -m mcp_server.server
# Streamlit playground:
streamlit run playground/app.pyRequires Python 3.13. Needs ANTHROPICAPIKEY and TAVILYAPIKEY in .env (see .env.example).
Architecture
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
MCP Automations: common questions
- Is MCP Automations MCP server safe?
- Mostly: it is graded B (84/100). Read the MCP Automations safety report
- How do I install MCP Automations?
- It runs remotely at mcp-automations.fly.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does MCP Automations need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is MCP Automations maintained?
- The last commit was 123 days ago (2026-07-04). The latest release is v0.1.0.
- Is MCP Automations up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does MCP Automations compare with other MCP servers?
- safety score 84/100 (higher than 68% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.