Claude Desktop setup
Use the mcp-remote configuration supplied by Era.
Apps → MCP generates mcp-remote configuration for command-launching clients such as Claude Desktop. Complete key creation first. Node and npx must be available.
Mac/Linux command form
Add this to Claude Desktop’s MCP configuration while preserving existing mcpServers entries:
{
"mcpServers": {
"era": {
"command": "npx",
"args": ["-y", "mcp-remote@latest", "https://app.getera.io/api/mcp", "--header", "x-api-key:<your era_ key>"]
}
}
}Windows command form
Era’s Windows example launches npx through cmd:
{
"mcpServers": {
"era": {
"command": "cmd",
"args": ["/c", "npx", "-y", "mcp-remote@latest", "https://app.getera.io/api/mcp", "--header", "x-api-key:<your era_ key>"]
}
}
}Apply your installation origin and private key. JSON itself does not hide credentials; do not share the actual-key file. Reload the server and inspect the tool list.
Try a read
Read the Era business overview. List waiting work without deciding approvals.Two Claude connections
Era has one MCP server: /api/mcp, named era. In Claude.ai and Claude Desktop, Settings → Connectors → Add custom connector, paste the address and sign in in the browser (OAuth); config-file clients connect with x-api-key. The workflow designer’s tools are on this server too.
If launch fails, inspect Node/npx; for 401, inspect key/header. Continue with MCP help and tool groups.