MCP setup
Create a key, connect the right server and verify with a read.
This guide connects Era’s business-record and memory server. The client uses its own AI account; an Era API key does not replace a model subscription.
Select workspace and key
Open Apps → MCP on web or desktop. Choose Create key on the Era server card. Copy its URL and the full key now; the key is shown once. Issuing it requires API-key management access.
Configure your client
Use the card’s /api/mcp URL as it is. Apply authentication from the client guide below. The header is x-api-key; Bearer also works. <your era_ key> is a placeholder.
Verify without changes
List the Era tools and read the accessible business overview.
Do not change records or send outbound messages.The client should load tools/list; inspect the era_overview read result. Adding an address does not establish that a real tool call succeeded.
Claude Code
HTTP command and header.
Codex
TOML and an environment-backed Bearer key.
Cursor
mcp.json and x-api-key.
Claude Desktop
mcp-remote and the Windows form.
VS Code
mcp.json with a secret input prompt.
Tools
Live catalogue versus generated schemas.
Rotate a key
Rotate key removes the old key; update every client using it. The new value is shown once. Retrying sign-in with a revoked key does not restore access.
Check failures
| Symptom | Check |
|---|---|
| 401 | Missing, invalid or rotated key; inspect header and URL. |
| 404 | Use the card’s actual API path, not /mcp, /mcp/personal or /mcp/org. |
| Tools list but operation fails | Module, role, row scope and input preconditions. |
| Waiting for approval | Decide the existing card; do not restart the call. |
| Stale tool list | Reconnect the client and load live schemas. |
Keep keys and customer-bearing config out of Git, chat and support screenshots. Permissions and MCP/CLI help explain further checks.