<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration on Devops Monk</title><link>https://blog.devops-monk.com/tags/integration/</link><description>Recent content in Integration on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/integration/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP in Claude Code: Connect to External Tools, Databases &amp; APIs</title><link>https://blog.devops-monk.com/2026/05/claude-code-mcp-protocol-guide/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-code-mcp-protocol-guide/</guid><description>Claude Code can read and write files, execute shell commands, and search your codebase. But here&amp;rsquo;s the problem: it lives in isolation. It can&amp;rsquo;t talk to your database. It can&amp;rsquo;t query your Jira board. It can&amp;rsquo;t inspect network requests in your running app. It can&amp;rsquo;t access your AWS infrastructure.
Without MCP, Claude Code is smart but limited.
With MCP (Model Context Protocol), Claude Code becomes a full participant in your development ecosystem—talking to databases, APIs, monitoring systems, and custom tools in real-time.</description></item></channel></rss>