Codex Delegate vs Plori
A side-by-side look at the Codex Delegate and Plori MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codex Delegate for coding agents work as a local process; choose Plori for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codex Delegate when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Choose Plori when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 43/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Codex Delegate | View Plori |
Tools & capabilities
Codex Delegate tools
No tool names declared yet. Check the project README from the listing page.
Plori tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codex Delegate
{
"mcpServers": {
"codex-delegate": {
"command": "npx",
"args": [
"-y",
"codex-delegate-mcp"
]
}
}
}
Plori
{
"mcpServers": {
"plori-ai-plori": {
"command": "npx",
"args": [
"-y",
"plori-mcp"
]
}
}
}
Frequently asked questions
Codex Delegate is categorized under Coding Agents and uses a local stdio subprocess. Plori belongs to Coding Agents and uses a local stdio subprocess. Pick Codex Delegate for coding agents work and Plori for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codex Delegate has no declared pricing — check the project's own site. Plori is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add codex-delegate and plori-ai-plori as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codex Delegate has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Plori has 57/100 (Good) with 6 views, 0 installs and 0 GitHub stars.