<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Integrations on Software - art</title>
		<link>https://softwareengineeringblog.com/tags/Integrations/</link>
		<description>Recent content in Integrations on Software - art</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>Laszlo Varga</copyright>
		
		
			<lastBuildDate>Thu, 08 Oct 2026 14:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://softwareengineeringblog.com/tags/Integrations/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Our Elementor AI Page Builder, Explained</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-our-elementor-ai-page-builder-explained/</link>
				<pubDate>Thu, 08 Oct 2026 14:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-our-elementor-ai-page-builder-explained/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/our-elementor-ai-page-builder-explained.webp&#34; alt=&#34;A minimalist indoor workspace featuring a blank laptop screen and a cappuccino in a modern setting.&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@anna-nekrashevich&#34;&gt;Hanna Pad&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/macbook-pro-on-white-table-7214629/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;A template&amp;rsquo;s own fonts and colors are only useful if the pages built from it actually keep them. At &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt;, that problem sits behind an Elementor AI page builder: pick &lt;a href=&#34;https://elementor.com/&#34;&gt;Elementor&lt;/a&gt; as a site&amp;rsquo;s page builder in the setup wizard, and the product generates real, native Elementor pages that match the chosen template&amp;rsquo;s own design, reachable from site creation, from the drawer, and from chat. This is how that builder works, end to end.&lt;/p&gt;</description>
			</item>
			<item>
				<title>A Multilingual WooCommerce AI Assistant</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-a-multilingual-woocommerce-ai-assistant/</link>
				<pubDate>Thu, 08 Oct 2026 13:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-a-multilingual-woocommerce-ai-assistant/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/a-multilingual-woocommerce-ai-assistant.webp&#34; alt=&#34;Perspective view of industrial shelves filled with organized plastic storage boxes in a warehouse.&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@zhengyang-tian-2152549665&#34;&gt;Zhengyang TIAN&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/industrial-storage-shelves-with-plastic-boxes-40068599/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;A store owner who already knows exactly what needs doing — raise a price, check what is low, see who bought what — should not have to translate that into admin-screen clicks before &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt; can help. That is the premise behind SimpleWP&amp;rsquo;s &lt;a href=&#34;https://woocommerce.com/&#34;&gt;WooCommerce&lt;/a&gt; AI assistant: a chat interface that runs a real online store in the words a store owner already uses, in their own language and their own currency. This is the engineering story of how a single team shipped that assistant across four languages at once, and what it took to keep every one of them honest.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Connecting AI Agents with MCP OAuth</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-connecting-ai-agents-with-mcp-oauth/</link>
				<pubDate>Thu, 08 Oct 2026 11:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-connecting-ai-agents-with-mcp-oauth/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/connecting-ai-agents-with-mcp-oauth.webp&#34; alt=&#34;Detailed view of a backlit laptop keyboard keys with blue LED lighting for tech concepts.&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@castorlystock&#34;&gt;Castorly Stock&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/black-and-white-computer-keyboard-4065748/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;An AI assistant that can act on a website needs more than an address to call. At &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt;, that need led to an MCP OAuth connection for the product&amp;rsquo;s site-management tools: an authorization flow that lets &lt;a href=&#34;https://claude.ai/&#34;&gt;Claude.ai&lt;/a&gt;, &lt;a href=&#34;https://chatgpt.com/&#34;&gt;ChatGPT&lt;/a&gt; and other MCP clients reach a user&amp;rsquo;s sites by signing in and clicking Allow, the same way any other app connects to an account. This is how that MCP OAuth flow was built, from serving the tools themselves to proving the whole exchange against a real client before shipping it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Building a Static Egress IP Relay</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-building-a-static-egress-ip-relay/</link>
				<pubDate>Thu, 08 Oct 2026 10:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-building-a-static-egress-ip-relay/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/building-a-static-egress-ip-relay.webp&#34; alt=&#34;From below of long thin identical blue cables connected to small round electrical connectors&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@brett-sayles&#34;&gt;Brett Sayles&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/patch-cables-plugged-in-patch-panel-4657267/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Every outbound call SimpleWP makes to a hosting partner has to arrive from somewhere that partner&amp;rsquo;s own system already trusts. At &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt;, calls to &lt;a href=&#34;https://wordpress.com/&#34;&gt;WordPress.com&lt;/a&gt;&amp;rsquo;s &lt;a href=&#34;https://wp.cloud/&#34;&gt;WP Cloud&lt;/a&gt; platform and to &lt;a href=&#34;https://dotroll.com/en/&#34;&gt;DotRoll&lt;/a&gt;&amp;rsquo;s &lt;a href=&#34;https://www.cpanel.net/&#34;&gt;cPanel&lt;/a&gt; hosting both rely on one static egress IP address, run by &lt;a href=&#34;https://simplewp.com/pages/about&#34;&gt;the engineers behind SimpleWP&lt;/a&gt; as a relay the team built and operates itself. This is the story of how that relay was designed, what one missing access path revealed once it shipped, and how the design evolved without ever changing what actually keeps it safe. A static egress IP relay sounds like a small piece of plumbing until the day a partner&amp;rsquo;s allowlist is the only thing standing between a working integration and a silent one.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
