Era MCP server
Connect business records, files and memory to Claude, Codex and other clients.
MCP lets an AI client call Era’s permitted tools. The external client uses its own model; Era checks the key owner’s current access before reading business data or executing an authorized operation.
Connection URL
https://app.getera.io/api/mcpFor your installation, use the origin shown under Apps → MCP. The plain address lists the named tools shared with chat/CLI and permitted connected-app tools. Send the key in x-api-key or Authorization: Bearer.
The key owner supplies access
This is not device pairing. Calls use the issuing person’s role, workspace and enabled modules. Selecting the client model does not widen this access.
Setup
Create a key, choose a client and make a first read.
MCP or CLI?
Remote-client connection versus a chat terminal.
Example prompts
Read first, then inspect a prepared operation.
Tool groups
Records, documents, files, memory and outcomes.
What you can do
Find and summarize accessible records, draft invoices/quotes, save outputs to Era Files and search sourced memory. Outbound sends, publishing or removal need the applicable approval outcome. Do not report an approval wait as success.
Other servers
| Server | Purpose | Authentication |
|---|---|---|
/api/mcp | Named Era tools and connected apps (workflow designer tools included). | Key from the MCP card, or browser sign-in (OAuth). |
/api/mcp?tools=full | Memory and full permitted module-action catalogue. | Same key. |
/api/mcp?tools=compact | Read tools, era_find_tools and era_call. | Same key. |
/api/mcp/serve/SERVER_ID | A created workflow MCP server. | That server’s settings. |
Adding outside servers into Era is the reverse direction: Settings → AI → MCP. See connection settings.
Reference
Generated schemas document the core Era tools. Actual tools/list varies with role, connections, catalogue and engine. A published tool count is not your account’s access count.