<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>mcp on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/mcp/</link>
    <description>Recent content in mcp on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/mcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Abbreviatory 0.3 Gives Coding Agents an MCP Server and Opens a Browser Demo</title>
      <link>https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/</guid>
      <description>Coding agents run tests all day. Every run prints thousands of lines, and the agent reads all of them, pays for all of them, and then often reads them again after a one-line change. Abbreviatory v0.3.0 lets the agent skip that. It&amp;rsquo;s now an MCP server, so an agent can ask it to run the tests and get back the short report instead: the failures with their messages, what changed since the last run, and one line when nothing did.</description>
    </item>
    
    <item>
      <title>How to Give a Coding Agent Short Test Reports Through the Abbreviatory MCP Server</title>
      <link>https://abbreviatory.com/how-to-give-a-coding-agent-short-test-reports-through-the-abbreviatory-mcp-server/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/how-to-give-a-coding-agent-short-test-reports-through-the-abbreviatory-mcp-server/</guid>
      <description>A coding agent fixing a bug runs the tests again and again. Change a line, run go test ./..., read the output, change another line. Each run of our sample suite prints 4,882 lines of go test -json events, 808 kB, and almost all of it says a test passed. The agent reads every line, every time, and pays for every line in its context window. By the tenth run most of its context is old test output.</description>
    </item>
    
  </channel>
</rss>
