TemprTempr
Blog

Notes from the Tempr team

How Tempr works, why it works that way, and what we learn running one product across every AI provider.

Subscribe via RSS Read the changelog

  1. 5 min read

    Dictating to a coding agent

    Voice input is out in the Tempr CLI, Tempr Chat for VS Code, JetBrains IDEs and Visual Studio, and the Tempr Code preview, transcribed on your own key.

    • Agents
    • CLI
    • Voice
  2. 5 min read

    What an MCP gateway does for a team

    One developer can wire up MCP servers by hand. A team needs five things from a gateway in between: credentials, sign-in, permissions, checks and a record.

    • MCP
    • Gateway
    • Security
  3. 5 min read

    Ask for a model, not a host

    Open-weight models run on many hosts under different ids. Gateway pools let you name the model once and run it on whichever of your providers serve it.

    • Gateway
    • Routing
  4. 5 min read

    Popular remote MCP servers, with sign-in filled in

    The Portal now lists 60 checked remote MCP servers and searches the MCP registry. What "checked" means, and why each member signs in as themselves.

    • MCP
    • Gateway
    • Security
  5. 4 min read

    Reasoning that survives a model switch

    Every provider returns reasoning in its own shape, and some need it back next turn. How Tempr returns one shape and keeps conversations working across models.

    • Gateway
    • Reasoning
  6. 4 min read

    When a provider retires an API

    Perplexity replaced its Sonar chat completions with a new Agent API, retired on September 27. What changed for Tempr users, and how Tempr handles retirements.

    • Gateway
    • Providers
  7. 5 min read

    Running Codex CLI on Claude, and every other model

    Codex CLI speaks OpenAI's Responses API. How Tempr Gateway's /v1/responses runs it on Claude, Gemini, DeepSeek and more, what carries over, and what doesn't.

    • Gateway
    • Codex
  8. 4 min read

    Every MCP tool call, through one place you control

    MCP gives coding agents real tools, plus tokens on every laptop and shared bot accounts. How Tempr's Gateway relays MCP so calls run as the right person.

    • MCP
    • Gateway
    • Security
  9. 4 min read

    Paid MCP tools: refused clearly, never paid

    Some MCP servers now charge per tool call, through x402 or MPP. Why Tempr doesn't pay, and how it makes the refusal clear instead of a confusing error.

    • MCP
    • Chat
    • CLI
    • Gateway
  10. 3 min read

    Putting a price ceiling on an agent run

    An agent run's cost can't be known in advance. How Tempr lets you, and your organization, cap what one run may spend and see which runs cost the most.

    • CLI
    • Chat
    • Portal
    • Budgets