<?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 AppJars</title><link>https://www.appjars.com/blog/tags/mcp/</link><description>Recent content in MCP on AppJars</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Oct 2026 12:22:30 -0300</lastBuildDate><atom:link href="https://www.appjars.com/blog/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Give your AI coding assistant the AppJars documentation</title><link>https://www.appjars.com/blog/appjars-docs-mcp-server/</link><pubDate>Thu, 15 Oct 2026 10:00:00 -0300</pubDate><guid>https://www.appjars.com/blog/appjars-docs-mcp-server/</guid><description>&lt;p>Ask a coding assistant to add a feature with a library it has never seen, and it will rarely
say &amp;ldquo;I don&amp;rsquo;t know&amp;rdquo;. It will write code that looks right: a plausible class name, a property key
that follows the usual conventions, a method that would make sense if it existed. Then the
application fails to start, or starts and quietly ignores the setting.&lt;/p>
&lt;p>AppJars is new. The modules, their Spring properties and their extension points were published
after most models were trained, so an assistant has nothing to go on but guesses. The answers
are in the &lt;a href="https://docs.appjars.com" target="_blank" rel="noopener">AppJars documentation&lt;/a>; the assistant just can&amp;rsquo;t see it.&lt;/p></description></item></channel></rss>