From d57df7ef884eb2abeecc49a16172ef423101a026 Mon Sep 17 00:00:00 2001 From: Victor Soria Date: Sun, 3 May 2026 22:23:56 -0500 Subject: [PATCH] docs(readme): add AI-native and MCP angle to intro - Add third tagline line highlighting AI agent modeling path - Add MCP server paragraph to 'What is ArchiPulse?' section --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 35c1ee2..a2e05a1 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@ **Enterprise Architecture models without vendor lock-in.** **Publish your ArchiMate models and explore, analyze and navigate them from a self-hosted web platform.** +**Or skip the modeling tool — describe your system to an AI agent and let it build the model for you.** Built on ArchiMate · Powered by Go · PostgreSQL · Open Source @@ -36,6 +37,8 @@ The result: your architecture is not a static file but **living, collaborative d ArchiPulse works alongside the tools architects already use — **Archi**, **archimate-editor**, or any AOEF-compatible tool. It adds the collaborative repository, the analytical layer, and the enrichment pipeline on top. +It also ships an **MCP server** (`archipulse mcp`) that lets any MCP-compatible AI agent — Claude, or others — operate the repository directly: create workspaces, model elements and relationships, query analytical views, and export AOEF, all through natural language. No file uploads, no manual modeling required. + --- ## Table of Contents