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

    • shapeless

      FirstClassTree
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.
      1
      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
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear boundaries between agents, runs, workflows, executions, billing, disk, and connections. The few potentially confusable pairs (e.g., get_run_result vs get_workflow_execution, invoke_agent vs run_workflow) are well-differentiated by their descriptions and operate on different entities.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (list_agents, create_workflow, get_run_result, etc.). Minor singular/plural variations (answer_pending_input vs list_pending_inputs) are logically motivated and do not break the pattern.

    Tool Count4/5

    With 25 tools, the set is on the heavy side, but each tool earns its place given the platform's breadth: agent lifecycle, run management, workflow CRUD and execution, billing, disk, and connections. No tool appears redundant or trivial, though the count is at the upper bound of comfortable.

    Completeness4/5

    Core operations for agents, runs, workflows, billing, and disk are well covered. Minor gaps exist, such as no delete_workflow, no cancel_workflow_execution, and no update_agent for renaming or reconfiguring, but these are edge cases that agents can likely work around or that are intentionally handled elsewhere.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources