Ephemeral

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Developer tools
• You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http ephemeral https://app.ephemer.al/mcp --header 'Authorization: Bearer {api_key}'

{
  "mcpServers": {
    "ephemeral": {
      "url": "https://app.ephemer.al/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

{
  "servers": {
    "ephemeral": {
      "type": "http",
      "url": "https://app.ephemer.al/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• Authorization secret HTTP header
  An Ephemeral API key as a bearer token, for clients that do not sign in with OAuth (those need only the URL). Create one under Keys in the dashboard; use a member key for agents.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• create_run

  Start an AI agent run in an isolated sandbox and return the run (status queued) at once. Give a prompt, or the name of a saved workflow. Poll with get_run or block with wait_for_run for the result. Every run has a cost cap (max_cost_micros) and a timeout, and is billed to the org

• get_run

  Read a run: status, output, error, cost and billing_pending. COST: while billing_pending is true (or the run is still going), cost_micros is PROVISIONAL and usually higher than the final cost; the result then has cost_final:false and a cost_note. Quote a cost only when cost_final

• wait_for_run

  Wait until a run finishes (succeeded, failed, cancelled, interrupted or timed_out) or the wait ends, then return the run. After the run finishes it keeps waiting, within the same time, until billing has settled (billing_pending false, normally a few seconds to about 20), so the c

• list_runs

  List the organization's runs, newest first, with a cursor for the next page. Each run has cost_final: when false, cost_micros is provisional (usually above the final cost) and billing is still settling.

• cancel_run

  Cancel a run that has not finished. Work already done is billed. Cancelling a finished run changes nothing.

• list_workflows

  List the organization's saved workflows (reusable run definitions). Each entry has the workflow's name and, when set, its description, input_schema (the shape of the input create_run expects) and output_schema (the shape of the JSON it returns), so you can call a workflow without

• get_workflow

  Read a saved workflow's definition: description, prompt, model, files, connections, limits and its input_schema and output_schema. Credentials are never included.

• list_models

  Find models. Returns a compact list (id, name, context_length, input and output USD per million tokens, zero_data_retention where known), the total count and the default model. There are hundreds of models, so filter with query (case-insensitive part of the id or name, e.g. "clau

• list_connections

  The organization's saved connections that a run may use, with type, allowed methods and tools. No URLs or secrets are returned. Reference one in create_run by name.

• save_workflow

  Create a workflow, or replace the one with this name (saving the same definition again changes nothing more). A workflow is a reusable run definition: start it with create_run and its name, or on a timetable with create_schedule. Connections must already be saved in the organizat

• delete_workflow

  Permanently delete a saved workflow. Runs already started are not affected; schedules that use it stop being able to start runs until it is saved again.

• list_schedules

  List the organization's schedules: each starts a saved workflow on a cron timetable. Includes the next start, the last run and the last error.

• get_schedule

  Read a schedule: timetable, time zone, input, cost cap, whether it is enabled, its next start and the outcome of its last start.

• create_schedule

  Start a saved workflow on a timetable. Needs an administrator key. Each start is a run billed to the organization, with the cost cap given here (or the default). Use preview_schedule first to check the timetable. A schedule pauses itself after repeated failed starts. An organizat

• update_schedule

  Change a schedule; only the fields you give change. Needs an administrator key. Set enabled to false to pause it and to true to resume it (resuming clears the failures that paused it). A new timetable counts from now.

• delete_schedule

  Permanently delete a schedule. Needs an administrator key. Runs it already started are not affected. To stop it for a while, pause it with update_schedule instead.

• preview_schedule

  Check a cron expression and time zone and return the next five start times (UTC), without saving anything.

• run_schedule

  Start the schedule's workflow now, outside its timetable, with the schedule's input and cost cap. Returns the queued run (follow it with wait_for_run); each call starts another run and is billed like any run.

• list_files

  List the files saved in the organization: id, name, size, content type and creation time. Reference a file by id in a run's or workflow's files. Read-only; upload and delete files through the REST API.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (ephemer.al) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 536 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 19 tool descriptions and found no hidden instructions to the AI

Compared with others in Developer toolsi

• More stars than 0% of the other 5735 servers in this category
• Published to the registry more recently than 62% of the other 5735 servers in this category
• Basic checks equal to or better than 27% of the other 5735 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo