Skip to main content
Glama
plori-ai

Plori

Official
by plori-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Plori

No user-submitted related servers found.

    Related Servers

    • softkiln

      softstars-as
      A
      license
      Not graded
      quality
      C
      maintenance
      Host 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

    • Terminal Session Manager

      danieldoalto
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.
      15
      -
    • openpouch by openpouch

      openpouchofficial

      openpouch
      A
      license
      A
      quality
      D
      maintenance
      Agent-native hosting: your agent deploys any folder to a live URL in one command — no account, no dashboard, no CAPTCHA — and hands the human a link plus a plain-language summary. Full deploy lifecycle as MCP tools (deploy, verify, logs, inspect, rollback), production approval human-only; static sites and full Node.js apps, open source (Apache-2.0).
      13
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Tools are organized into clear resource domains — agents, workflows, runs, billing/disk, and OAuth — so most choices are obvious. The main ambiguity is get_workflow vs get_workflow_version, and to a lesser extent get_agent vs create_agent's get-or-create behavior, which an agent could misselect despite helpful cross-references.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: create_agent, list_workflows, cancel_run, empty_trash, answer_pending_input. The get/list split is applied uniformly across agents, workflows, and executions, making the naming predictable.

    Tool Count3/5

    At 25 tools, the server sits at the heavy end of the scale. Each tool is individually justified by the broad scope — agents, workflows, runs, billing, disk, and connections — but the total surface feels more like several subdomain APIs bundled together than a tightly scoped set.

    Completeness3/5

    Agent and run lifecycle coverage is strong, but the workflow lifecycle has notable gaps: there is no delete_workflow, and no explicit activate/publish tool even though edit_workflow warns that edits do not activate the draft. Billing, disk, and connection surfaces are read-mostly, which is acceptable but leaves workflow management incomplete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources