Plori

- **Manage agents**— Ask to`list_agents`, inspect agent details, create or delete agents, and select the model an agent runs on. - **Run and monitor agents**— Invoke an agent via`run_agent`, list or fetch past run results, and cancel in-flight runs. - **Handle approvals**— List an agent's pending questions with`list_pending_questions`and answer them to keep work moving. - **Schedule deferred work**— Use the scheduling tools to queue a run so an agent executes later while you're away. - **Build and run workflows**—`list_workflows`,`create_workflow`,`edit_workflow`, and`run_workflow`to define, refine, and execute multi-step agent workflows. - **Check account status**— Query`get_credits`,`get_usage`,`get_disk`, and`list_connections`to review balances and connected OAuth providers. **plori (plori.ai): a cloud AI agent with its own persistent environment - durable disk, real CLI tools, and memory.** [ploriprovides the agent: each one gets a persistent machine with a real disk, real tools, and memory of its own. Idle agents scale to zero. You talk to your agents in the web app, or drive them from your own tools over MCP and REST. This repository is the integration front door. The product itself lives at](https://plori.ai)[plori.ai; the remote MCP server lives at`https://api.plori.ai/mcp`. plori is a**remote**MCP server (streamable HTTP). There is nothing to install or run locally. Sign-in happens in your browser via OAuth 2.1 the first time your client connects; headless environments can use an API key instead. ``` `claude mcp add --transport http plori https://api.plori.ai/mcp` ``` Use the one-click](https://plori.ai)[Add to Cursorbutton, or add manually:`Settings -> MCP -> Add server`with URL`https://api.plori.ai/mcp`. ``` `code --add-mcp '{"name":"plori","type":"http","url":"https://api.plori.ai/mcp"}'` ``` ``` `codex mcp add plori --url https://api.plori.ai/mcp codex mcp login plori` ``` Codex auto-detects plori's OAuth on`login`. One-install alternative with the skill bundled:`codex plugin marketplace add plori-ai/codex-plugin`then`codex plugin add plori@plori`. Follow](https://plori.ai/mcp)[llms-install.md, written for Cline's automated installer. Native streamable-HTTP clients connect to`https://api.plori.ai/mcp`directly. Clients that only speak stdio can bridge with the](https://github.com/plori-ai/plori/blob/HEAD/llms-install.md)[`plori-mcp`npm package(a thin wrapper around`mcp-remote`with the endpoint pinned; this repository is its source): ``` `npx plori-mcp # headless / CI: authenticate with an API key instead of the OAuth flow npx plori-mcp --header "Authorization: Bearer plori_sk_..." # equivalent, without the wrapper: npx mcp-remote https://api.plori.ai/mcp` ``` API keys are minted in](https://www.npmjs.com/package/plori-mcp)[Dashboard -> Settingson a registered account. The](https://plori.ai/dashboard/settings)[plori CLIis not an MCP client. It is a door of its own, and it opens the same live session the web app shows: the recent history, a prompt, streaming output, and the approval queue in one place. A turn you send in the terminal appears in an open browser tab as it streams. ``` `curl -fsSL https://plori.ai/install.sh | sh plori login && plori attach <agent-name>` ``` The installer drops one static binary in`~/.local/bin`and needs no Node; if that directory is not on your PATH yet, the script prints the line to add.`npm i -g @plori/cli`works too. The argument to`attach`is an agent name, an agent id, or a session id, so a session id copied out of the web app works on its own.`Ctrl-D`detaches and leaves the run going on the server. The terminal does not give the agent access to your local files. The shell, the disk, and the files are the agent's own cloud environment. List my plori agents and tell me how many credits I have left. You should see`list_agents`and`get_credits`tool calls and a real answer. The server exposes 24 tools in five groups: - **Agents**: list, inspect, create, and delete agents; pick the model an agent runs. - **Runs**: invoke an agent and read its reply (blocking or fire-and-forget), list runs, fetch a past result, or cancel an in-flight run. - **Human-in-the-loop**: list an agent's pending questions and answer them. - **Scheduling**: schedule a deferred run so an agent works while you are away. - **Workflows**: list every workflow or filter by holding agent / the unassigned bucket (`list_workflows`with optional`agent_id`UUID or`"none"`), read one with the step projection pinned for execution (`get_workflow`) or read an exact version's full definition (`get_workflow_version`), edit a draft under compare-and-swap (`edit_workflow`), create one for an agent to build (`create_workflow`, with optional`agent_id`), run a built workflow now as a real, billed execution (`run_workflow`), and read recent execution history (`list_workflow_executions`) or poll one execution's status, timing, credits, and per-step input/output payloads (`get_workflow_execution`). Account reads round out the set:`get_credits`,`get_usage`,`get_disk`, and`list_connections`— your third-party OAuth providers with status, authorization and expiry times, and the scopes configured for each. Tokens and client secrets are never returned. Costs: creating and running agents spends plori credits from your account. Reading (lists, results, balances) is free. The](https://www.npmjs.com/package/@plori/cli)[pricing pagehas the details; revoke a client's access any time in your client's settings, or revoke the API key in Dashboard -> Settings. - Front door:](https://plori.ai/pricing)[plori.ai/agents.md - Site index:](https://plori.ai/agents.md)[plori.ai/llms.txt - Skill:](https://plori.ai/llms.txt)[SKILL.md(index:`/.well-known/agent-skills/index.json`) - MCP server card:`https://api.plori.ai/mcp/server-card` - OAuth discovery: RFC 9728 protected-resource metadata on`api.plori.ai`, dynamic client registration supported - Registry entry:](https://plori.ai/.well-known/agent-skills/plori/SKILL.md)[`ai.plori/plori`in the official MCP Registry Every page on plori.ai is also served as Markdown: append`.md`to the path or send`Accept: text/markdown`. - ](https://registry.modelcontextprotocol.io/v0/servers?search=ai.plori/plori)[Connect guide(per-client, kept current) - ](https://plori.ai/mcp)[Docs - ](https://plori.ai/docs)[Privacyand](https://plori.ai/privacy)[terms - Questions:](https://plori.ai/terms)[agent@plori.ai This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases. Create crafted UI components inspired by the best 21st.dev design engineers. Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively . MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent ALAPI MCP Tools,Call hundreds of API interfaces via MCP AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references. APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API. One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth. Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB](https://github.com/plori-ai/plori/blob/HEAD/mailto:agent@plori.ai)