Plori
OfficialRelated Servers
Alternatives to Plori
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOutbound-only remote shell, detached long-running jobs, and temporary file courier for AI agents. Hosted Streamable HTTP plus stdio via npx -y @aicommander/mcp.111MIT

PoYo MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceLocal stdio bridge to the hosted PoYo MCP server, enabling discovery and execution of AI models via chat, generation tasks, and agent skills.1MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to run Playwright-compatible browser automation over stdio or Streamable HTTP, covering research, testing, persistent login profiles, Chrome extensions, proxy matching, and humanized interactions. It ships as npm and Docker packages for cross-platform deployments.485 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a Playwright-compatible browser (with humanized mouse, keyboard, and scroll behavior, persistent profiles, extensions, and GeoIP-aware proxies) to research the web, automate daily tasks, and run tests, with unchanged upstream @playwright/mcp tools plus two local introspection tools. It installs via npm or Docker and speaks stdio or Streamable HTTP.485 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to automate real browser sessions through Playwright-compatible tools, including web research, testing, persistent profiles, proxy matching, and humanized interactions, with npm, Docker, stdio, and Streamable HTTP deployment options.485 npmMIT
- AlicenseNot gradedqualityCmaintenanceHost apps built with AI: deploy to a live HTTPS URL, custom domains, managed sign-in, secrets and backups. Hosted remote MCP server at https://softkiln.com/mcp/ — this repository is its plugins and skills.MIT
TDQS
Scored across 24 tools
Tools are largely distinct by resource and action, but get_run_result and get_workspace_worker overlap when reading a worker's run reply, and list_runs vs list_workspace_workers are similar list operations. The descriptions clarify boundaries, but an agent could still mix them up in edge cases.
All tool names use consistent snake_case verb_noun patterns, such as get_workspace_changeset, accept_workspace_changeset, list_workspaces, and cancel_run. No mixed conventions or erratic verb styles are present.
24 tools is heavy for an MCP server and sits in the borderline 16-25 range. While the domain is complex, the set could likely be consolidated, and the count feels over-extended for typical agent interactions.
The core lifecycle for workspaces, workers, changesets, files, runs, and pending inputs is well covered, with few dead ends. Minor gaps exist, such as no explicit update_workspace or delete_workspace_file, but agents can generally work around them.