Server data from the Official MCP Registry
Create and drive plori cloud agents (each an AI agent on its own cloud computer) over MCP.
Create and drive plori cloud agents (each an AI agent on its own cloud computer) over MCP.
Remote endpoints: streamable-http: https://api.plori.ai/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ai-plori-plori": {
"url": "https://api.plori.ai/mcp"
}
}
}From the project's GitHub README.
Give your AI agent its own cloud computer.
plori hosts agents: each one gets a persistent machine with a real disk, real tools, and memory that survives between conversations. 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
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 Code
claude mcp add --transport http plori https://api.plori.ai/mcp
Cursor
Use the one-click Add to Cursor button, or add manually:
Settings -> MCP -> Add server with URL https://api.plori.ai/mcp.
VS Code
code --add-mcp '{"name":"plori","type":"http","url":"https://api.plori.ai/mcp"}'
Cline
Follow llms-install.md, written for Cline's automated installer.
Any other client
Native streamable-HTTP clients connect to https://api.plori.ai/mcp directly. Clients
that only speak stdio can bridge:
npx mcp-remote https://api.plori.ai/mcp
# headless / CI: authenticate with an API key instead of the OAuth flow
npx mcp-remote https://api.plori.ai/mcp --header "Authorization: Bearer plori_sk_..."
API keys are minted in Dashboard -> Settings on a registered account.
Ask your client:
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 15 tools in four groups:
Costs: creating and running agents spends plori credits from your account. Reading (lists, results, balances) is free. The pricing page has the details; revoke a client's access any time in your client's settings, or revoke the API key in Dashboard -> Settings.
The machine-readable entry points:
/.well-known/agent-skills/index.json)https://api.plori.ai/mcp/server-cardapi.plori.ai, dynamic
client registration supportedai.plori/plori
in the official MCP RegistryEvery page on plori.ai is also served as Markdown: append .md to the path or send
Accept: text/markdown.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.