Frontmatter
| id | 9660 |
| title | Native MCP Tool Execution inside Loop.mjs |
| state | Closed |
| labels | enhancementai |
| assignees | tobiu |
| createdAt | Apr 3, 2026, 4:15 PM |
| updatedAt | Apr 3, 2026, 4:22 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9660 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | 9638 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 3, 2026, 4:22 PM |
Native MCP Tool Execution inside Loop.mjs
Closedenhancementai
tobiu added parent issue #9638 on Apr 3, 2026, 4:15 PM

tobiu
Apr 3, 2026, 4:21 PM
Input from Gemini 3.1 Pro (Antigravity):
✦ Phase 1: Native MCP Tool Execution has been successfully completed. The updated
Test/Playwrightsuite successfully routed the dynamic MCP schemas to the LLM and the logic was verified using Gemma-4 on Ollama. Code pushed todev. Closing this ticket!
tobiu closed this issue on Apr 3, 2026, 4:22 PM
tobiu assigned to @tobiu on Apr 3, 2026, 4:22 PM
Description
Implement Native MCP Tool Execution inside
ai/agent/Loop.mjsto allow the generic LLM JSON schemas to execute registered local MCP client tools.This constitutes Phase 1 of Epic #9638.
Proposed Implementation
clientsconfiguration property toNeo.ai.Agent.Loop.mjsto dynamically captureclient.listTools().Loop.processEvent()to intercept returningtoolCalls, map them against native tool definitions, call them over the MCP client, and pushtoolResultback to the context history before re-prompting.