>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3561079. --> Reported by: [yautja_cetanu](https://www.drupal.org/user/626050) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Title: </strong>Content Classification Agent<br> <strong>Short Description: </strong>Agents can read a specific article and classify it based on the external thesaurus of terms. They can create new taxonomy if needed.<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Due Date:</strong> 01/13/2026<br> <strong>Additional Collaborators: </strong><br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><strong>Goals:</strong></p> <ul> <li>We first show how to build the AI Agents yourself using flowdrop UI, standard agents, Tools API, MCP and maybe guardrails. The main goal is to show off agent building not the best recipe or approach to this problem.</li> <li>We should it working with the chatbot and maybe making the change to a single page.</li> <li> This might also work nicely with Field Widget Actions </li> <li>We can then show a recipe of it working with a proper workflow approach. (But not setting that up from scratch) and how it could be automated across all content or on cron or on triggers).</li> </ul> <p><strong>Basic Version of this</strong></p> <ul> <li>An AI Agent is able to look across all the information on a piece of content and find classify it according to an MCP endpoint that is linked to a central Thesauras.</li> <li>Given the size of the thasaurus it might need a mixture of RAG or multiple agents.</li> <li>This could be a chatbot looking at the page you're on. Or we could use field widget actions for this.</li> <li>It can present the suggested changes on the page, or on a similar moderation page.</li> <li>Information can be found here: <a href="https://op.europa.eu/en/web/eu-vocabularies/det">https://op.europa.eu/en/web/eu-vocabularies/det</a></li> <li>Need to pick a page to classify but we could use: <a href="https://op.europa.eu/en/web/webguide/alternative-text">https://op.europa.eu/en/web/webguide/alternative-text</a> </li> </ul> <p><strong>Advanced version:<br> </strong></p> <ul> <li>We can have bulk classification tools or "Autonamous agents" that check things whenver the page changes or the thesaurus changes.</li> <li> This could be combined with the Context Control Center to handle the location of this endpoint and become a Drupal CMS Recipe. </li> </ul> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> > Related issue: [Issue #3561074](https://www.drupal.org/node/3561074)