Rtkcontext Mcp
Compress or manage bloated OpenAI Codex agent context through a paid remote MCP that returns verdicts, receipts, and usage logs.
Overview
RTK Context Compressor is a MCP server for the Operate phase that provides a remote OpenAI Codex context compressor with verdicts, receipts, and usage logs.
What is this MCP server?
- RTK Context Compressor MCP for OpenAI Codex context compression
- Paid remote streamable-http at rtkcontext.clauxel.com with Bearer auth
- Returns verdicts, receipts, and usage logs for compression runs
- Registry tags: rtkcontext, openai-codex-context-compressor, remote-mcp, paid-mcp, agent-tools
- Repo github.com/clauxel/rtk-context-compressor-mcp (v1.0.0)
- Registry version 1.0.0
- Remote: https://rtkcontext.clauxel.com/mcp (streamable-http)
- Authorization header required (Bearer from product website)
What problem does it solve?
Long Codex and agent sessions hit context limits and waste tokens, and you need a managed compressor with auditable usage.
Who is it for?
Solo builders on OpenAI Codex or similar stacks who repeatedly hit context ceilings and want a paid remote compressor MCP with receipts.
Skip if: Teams on short one-shot prompts with tiny repos, or users who refuse remote paid context services.
What do I get? / Deliverables
After MCP registration with a Bearer token, you can run context compression through the remote service and use verdicts and logs to keep Codex workflows stable.
- Remote context compression operations via MCP
- Verdicts, receipts, and usage logs
- Registry v1.0.0 metadata and GitHub reference implementation
Recommended MCP Servers
Journey fit
Context pressure shows up hardest in long-running coding sessions and production iteration loops, which fits Operate when you tune how agents consume tokens day to day. Iterate is the shelf because RTK Context Compressor is explicitly an OpenAI Codex context compressor—ongoing refinement of what stays in the window, not initial feature coding.
How it compares
Codex-focused context compressor MCP—not a local ripgrep skill or generic chat summarization prompt.
Common Questions / FAQ
Who is RTK Context Compressor for?
Indie developers using Codex-class agents on large codebases who need remote context compression with logged verdicts and usage.
When should I use RTK Context Compressor?
Use it in Operate when sessions grow unwieldy, instructions get dropped, or token spend spikes and you want compressor tooling via MCP.
How do I add RTK Context Compressor to my agent?
Obtain a Bearer token from Clauxel, configure https://rtkcontext.clauxel.com/mcp as streamable-http in your MCP client, and authorize each request.