Token Saver for Claude and Codex

Open the always-on startup page before first connection. It wakes the backend and tells you when to retry your MCP client.

https://tryelisai.com/mcp

Use the Claude endpoint for Claude Code and the OpenAI endpoint for Codex or ChatGPT-compatible MCP clients.

Claude: https://api.tryelisai.com/api/mcp/claude
Codex/OpenAI-compatible: https://api.tryelisai.com/api/mcp/openai

Paste this command and then run a normal prompt with Token Saver enabled:

claude mcp add --transport http elis-token-saver https://api.tryelisai.com/api/mcp/claude

For campaign tracking, append a referral and UTM source to the server URL:

claude mcp add --transport http elis-token-saver "https://api.tryelisai.com/api/mcp/claude?ref=YOURCODE&utm_source=claude"

In a Codex or OpenAI-compatible host that accepts remote MCP servers, add this server URL:

https://api.tryelisai.com/api/mcp/openai

Referral links work the same way:

https://api.tryelisai.com/api/mcp/openai?ref=YOURCODE&utm_source=codex

Start with start_elis_token_saver_plan, execute the returned next_task in the host, optionally submit your own decomposition when requested, call get_next_elis_task with a compact result and usage, then call finish_elis_plan.

1. start_elis_token_saver_plan({ goal, ref?, utm_source? })
2. submit_elis_task_plan({ plan_id, tasks }) // only when start asks
3. get_next_elis_task({ plan_id, previous_result, usage })
4. finish_elis_plan({ plan_id, final_answer, usage })

For signed-in users, a plan that finishes successfully is stored privately in your org/personal Elis scope as a proven chain, so a similar future goal replays the known-good task sequence instead of re-planning — fewer wasted host tokens. Every finish response discloses this in chain_tracking. Report honest previous_result.status (ok/failed/blocked): failed tasks are retried, then the remaining plan is revised (transition, plan_revision). A successful finish also returns a ~20-token chain_hint you may remember and pass back on a future start for direct recall — never store full chains in host memory.

// opt a plan out of storage/recall
start_elis_token_saver_plan({ goal, constraints: { no_store: true } })
// direct recall of a proven chain on a similar goal
start_elis_token_saver_plan({ goal, chain_hint: "elis_chain:<sig>:<plan_id>" })

OAuth sign-in is required in production. When a plan returns payment_method_required, open Elis Billing, attach a payment method, then retry the same Token Saver request under the linked account.

https://app.tryelisai.com/billing