McpMCP guides
MCP versus era CLI
Client tool calls and session-terminal commands for the same jobs.
Business access is enforced on the server. Choose based on the working environment and how you want to supply input.
| Topic | MCP | era CLI |
|---|---|---|
| Start | Client server configuration. | Era Desktop chat terminal. |
| URL | Card’s /api/mcp. | Desktop-supplied local /era/mcp. |
| Identity | MCP key owner. | Temporary chat person/workspace session. |
| Input | Tool call matching a schema. | Field flags or JSON file/stdin. |
| Catalogue | tools/list. | era tools. |
| Output | MCP content/result body. | Compact JSON or --text; exit code. |
| Local file | Content or an authorized save flow is needed. | file save resolves a local path. |
| Approval | Applicable send/publish/remove decisions. | Same business rules. |
One read, two inputs
MCP records_find input:
{"type":"customer","q":"Demo","limit":10}CLI:
era records find customer --q "Demo" --limit 10This example belongs to the named catalogue (the plain /api/mcp); full module-catalogue tool names differ. Use current live schemas in both interfaces.
Choose an interface
Use CLI for an Era engine working with terminals/local files. Configure MCP for Claude, Codex, Cursor or another compatible client outside Era. Neither removes role, row-scope or approval requirements.
Keep keys distinct
Do not substitute a remote MCP key for a CLI session key. The CLI accepts only Desktop’s local chat door; it is not a general remote API client.