EDF MCP
Related Servers
Alternatives to EDF MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets Claude Code and other MCP clients drive the SEO Content Machine desktop workspace on the same machine: starting and running tasks that scrape search results, crawl a site's internal links, pull Google Maps listings with ratings and reviews, download archive.org copies, extract page values into CSV, and add or update SEO Workspace pages, then read their results.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a supported web-chat AI client to control a local Windows computer through MCP using explicit, user-authorized tool calls for file, browser, shell, Git, and optional desktop operations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI assistants to control a Windows computer through GUI automation, file and process operations, PowerShell commands, durable background jobs, and binary file transfer with downloadable exports.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP agents to drive Windows applications by targeting individual windows—clicking, typing, scrolling, dragging, and reading accessibility trees or screenshots—without stealing the user's focus, mouse, or keyboard. Runs entirely locally alongside the user, with per-app approval and no cloud account or usage limits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Windows users to securely bridge compatible cloud LLM MCP services to local applications, allowing discovery and per-app authorization so approved desktop apps can be started or closed via MCP tool calls. It blocks high-risk system tools and stores connection tokens with Windows DPAPI encryption.5Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to control and interact with a local Windows computer through authenticated MCP tools, including file operations, shell commands, process management, HTTP requests, and system/media inspection.-
TDQS
Scored across 13 tools
Tools are mostly distinct: direct lookups (edf_dns_lookup, edf_whois_lookup) are separated from background jobs (edf_check_domains), and manual app results (edf_get_app_results) from automated job results (edf_get_job). Some potential overlap remains between edf_check_domains and the direct lookup tools, but descriptions clarify when to use each.
All tools use a consistent edf_ snake_case prefix with predictable verb_noun or noun_verb forms. Minor variations like edf_status and edf_launch are still clear and follow the same prefix convention.
13 tools is well-scoped for an EDF automation/domain-checking server, covering status, launch, config, lookups, job lifecycle, export, and crawl without excessive surface.
The job lifecycle is well covered (start, list, get, cancel, export) alongside direct lookups, config read, crawl, and Ahrefs rating. Minor gaps exist, such as no job deletion/purge and configuration is read-only, but these are likely intentional or workable.