Ephemeral Buffer MCP Server (ephemeral-buffer)
Ephemeral Buffer is an MCP server and command-line client for capturing command output in a bounded, searchable buffer. Coding agents can search captures and retrieve relevant portions instead of carrying entire build and test logs in their conversation context.
Quick start
Requires Python 3.10 or newer. Install the package in an isolated environment.
macOS and Linux
python3 -m venv .venv
.venv/bin/python -m pip install --upgrade pip
.venv/bin/python -m pip install ephemeral-buffer-mcp
Configure your MCP client using the user guide. For an isolated
server, the server and ephbuf must use the same unique session ID. On
macOS/Linux, export the ID before starting Codex with the launcher installed in
the virtual environment:
export EPHEMERAL_SESSION_ID=quick-start-session
.venv/bin/codex-ephemeral
Set the same value in another MCP client's server environment. Then capture
command output with ephbuf, passing the same ID.
macOS and Linux
.venv/bin/python -c 'print("Hello from a captured command")' 2>&1 |
EPHEMERAL_SESSION_ID=quick-start-session .venv/bin/ephbuf --label "quick start"
Windows installation steps are in the user guide's Windows support section. Windows runtime behavior isn't covered by CI; that section describes the unverified CLI capture and process-control paths.
The agent can then search the capture and retrieve bounded slices through the MCP tools.
Context reduction in one agent comparison
In a five-repetition gpt-6-luna comparison run on 2026-10-09, mean MCP
tool-response bytes fell from 6,681 to 1,501 (77.5%); the Codex context proxy
fell from 23,910 to 17,643 bytes (26.2%). This is a result from one workload,
not a general savings guarantee. The context figure is a prompt/event-envelope
proxy, not the model's internal context size. See the benchmark methodology
and comparison details.
Documentation
| Topic | Document |
|---|---|
| Installation, client setup, and privacy | User guide |
| MCP tools and advanced workflows | Tool reference |
| Data flow | Architecture |
| Benchmark commands, metrics, and comparisons | Benchmarks |
| Runtime configuration and operations | Operations guide |
| Development setup and contribution workflow | Contributing |
| Release history | Changelog |
Metadata
Release files for ephemeral-buffer-mcp 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ephemeral_buffer_mcp-0.10.0.tar.gz | 140.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ephemeral_buffer_mcp-0.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 285.7 kB
Release files / ephemeral_buffer_mcp-0.10.0.tar.gz
| Download URL | ephemeral_buffer_mcp-0.10.0.tar.gz |
|---|---|
| Size | 140.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b63f7a0f1078c6ef8d3115bef8c8d6fc95f248e17a2d0962c043515240e55b17
|
|
BLAKE2b-256 checksum How to use checksums |
a9f96a02fb0d0f718f527557080af01172a62073089c234eee11555112445f9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / ephemeral_buffer_mcp-0.10.0-py3-none-any.whl
| Download URL | ephemeral_buffer_mcp-0.10.0-py3-none-any.whl |
|---|---|
| Size | 145.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47455babe5b91b8080ce23dfed7bb30dbaad2726c6ef5db7c8e771cf315c775e
|
|
BLAKE2b-256 checksum How to use checksums |
7136fec64de2ecc53f81ce0490f7fd64f98891424541ae28a6104a6d238479dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency log