Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://erp.eyeot.fr/api/v1/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.termi24-eyeot-erp https://erp.eyeot.fr/api/v1/mcpRun in a terminal.
{ "mcpServers": { "io.github.termi24-eyeot-erp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://erp.eyeot.fr/api/v1/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
eyeot-mcpOfficial stdio ↔ HTTP bridge for the eyeot ERP MCP server.
~600 business tools, one pip install.
ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.
Landing page · Docs · PyPI · Issues
pip install eyeot-mcp # 1. install the bridge
eyeot-mcp login # 2. authenticate via browser (OAuth Device Flow)
Then paste into your Claude Desktop config:
{
"mcpServers": {
"eyeot": {
"command": "eyeot-mcp"
}
}
}
Restart Claude Desktop. Done. Ask: "List my last 5 invoices."
Config location · macOS
~/Library/Application Support/Claude/claude_desktop_config.json· Windows%APPDATA%\Claude\claude_desktop_config.json
The eyeot ERP exposes ~600 business actions — CRM, sales, stock, maintenance, HR, finance, IT service management, GED, RGPD compliance, plus 6 V2 marketplace modules (POS, delivery & routing, recruitment, BPM, field service, supply chain) — as MCP tools over HTTPS.
But Claude Desktop, Cursor, and most local agents only speak MCP over stdio.
eyeot-mcp is the missing piece between them.
flowchart LR
A["🤖 Claude Desktop<br/>Cursor / custom agent"] -- "JSON-RPC<br/>over stdio" --> B["📦 eyeot-mcp<br/>(this package)"]
B -- "HTTPS POST<br/>Bearer token" --> C["🏢 eyeot ERP<br/>(your tenant)"]
C -. "Auth · RBAC · audit<br/>multi-tenant isolation<br/>license guard" .-> C
style A fill:#eef2ff,stroke:#6366f1,color:#1e293b
style B fill:#f0fdf4,stroke:#10b981,color:#065f46
style C fill:#fef3c7,stroke:#f59e0b,color:#78350f
Zero business logic in the bridge. Everything happens server-side — auth, RBAC, audit logging, license enforcement, multi-tenant isolation, idempotency. The CLI is ~290 lines of Python standard library. You can audit it in 10 minutes.
After install, your MCP client gets access to actions like:
…and ~590 more, auto-generated from the OpenAPI spec.
Two modes, same Bearer header on the wire, same Authorization decorator server-side.
For Claude Desktop, Cursor, personal agents.
eyeot-mcp login
Opens browser → approve → done. Credentials saved to ~/.eyeot-mcp/config.json (mode 0600).
eya_<base64> access + eyr_<base64> refreshloginFor CI/CD agents, batch jobs, server-to-server.
{
"mcpServers": {
"eyeot": {
"command": "eyeot-mcp",
"env": { "EYEOT_TOKEN": "eyk_xxx_xxx" }
}
}
}
Issued by an org admin from the eyeot ERP settings panel.
eyk_<prefix>_<secret>OAuth 2.1 + PKCE
Public clients use PKCE S256. Refresh rotation with replay detection.
Server-side RBAC
Every tool call goes through the same @permissions_required decorators as the UI.
Full audit trail
Every action logged with user + tenant + IP. RGPD-compliant retention.
License grace
Subscription lapsed? GETs still work so the agent can inform you. POSTs return 402 with activate_url.
Local credentials stored at
~/.eyeot-mcp/config.jsonwith file mode0600(POSIX). On Windows, file ACLs apply. No telemetry, no phone-home.
Point the bridge at any eyeot deployment with --base-url:
eyeot-mcp --base-url https://erp.example.com login
{
"mcpServers": {
"eyeot": {
"command": "eyeot-mcp",
"args": ["--base-url", "https://erp.example.com"]
}
}
}
Same protocol, same auth, your infra.
eyeot-mcp as a child process, exchanges JSON-RPC 2.0 over its stdin/stdout pipes.POSTs the JSON to ${base_url}/api/v1/mcp with Authorization: Bearer <token>.2024-11-05 and auto-generates ~600 tools from the OpenAPI spec — initialize, tools/list, tools/call all work exactly as MCP clients expect.No state in the bridge. No protocol translation beyond transport. No surprises.
2024-11-05 (negotiated server-side)./api/v1 (stable). Breaking changes ship as /api/v2.MIT — fork it, package it, audit it, build on top of it.
The eyeot ERP backend is a separate, proprietary product of Eyeot Software. This bridge is open-source so anyone can audit it, fork it, package it for their distro, or use it as a reference for building their own MCP clients.
Multi-tenant, AI-native ERP for SMBs. Built to be operated by AI agents from day one.
Every action you can do in the UI, you can do via this bridge.
🌐 erp.eyeot.fr · ✉️ [email protected]
ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.
{ "mcpServers": { "io.github.termi24-eyeot-erp": { "url": "https://erp.eyeot.fr/api/v1/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Eyeot ERP เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-09 ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.