Skip to content

feat: built-in VoidLLM management MCP as default server entry#31

Merged
christianromeni merged 1 commit intomainfrom
feat/builtin-mcp-server
Mar 29, 2026
Merged

feat: built-in VoidLLM management MCP as default server entry#31
christianromeni merged 1 commit intomainfrom
feat/builtin-mcp-server

Conversation

@christianromeni
Copy link
Copy Markdown
Contributor

Summary

The VoidLLM management MCP server (list_models, get_usage, list_keys, etc.) now appears as a built-in server alongside external MCP servers — visible in the UI, discoverable via Code Mode tools, and callable from WASM-sandboxed JS.

  • Built-in server record with source="builtin" created idempotently at startup
  • In-process dispatch via callBuiltinTool — 0ms, no HTTP needed
  • Always accessible — skips MCP access check (no explicit grant needed)
  • UI badge "Built-in" (read-only, like YAML servers)
  • Pre-cached tools in memory + DB for warm restarts
  • SSE probe skips built-in server (no URL to probe)

Test plan

  • go test ./... -race — all packages green
  • list_servers returns "voidllm" with tool_count=6
  • search_tools finds management tools (list_models, get_usage)
  • execute_code calls tools.voidllm.list_models({}) — 0ms in-process
  • UI shows "Built-in" badge, server is read-only
  • Code review + security audit (0 open findings)

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 29, 2026

Codecov Report

❌ Patch coverage is 56.94444% with 31 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
internal/app/app.go 0.00% 18 Missing ⚠️
internal/mcp/server.go 0.00% 6 Missing ⚠️
internal/db/mcp_servers.go 78.26% 3 Missing and 2 partials ⚠️
internal/api/admin/mcp_proxy.go 86.66% 1 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

The VoidLLM management MCP (list_models, get_usage, list_keys, etc.) now
appears as a built-in server alongside external MCP servers.

- Visible in MCP Servers UI with "Built-in" badge (read-only)
- Discoverable via list_servers, search_tools
- Callable from Code Mode via tools.voidllm.list_models({})
- In-process dispatch (0ms, no HTTP) via callBuiltinTool
- Always accessible (no MCP access entry needed)
- DB record with source="builtin" created idempotently at startup
- Tools pre-cached in memory + persisted to DB for warm restarts
@christianromeni christianromeni force-pushed the feat/builtin-mcp-server branch from c24108d to c03c0de Compare March 29, 2026 14:27
@christianromeni christianromeni merged commit 6b0596c into main Mar 29, 2026
6 checks passed
@christianromeni christianromeni deleted the feat/builtin-mcp-server branch March 29, 2026 14:46
clawbolt pushed a commit to clawbolt/voidllm that referenced this pull request Apr 3, 2026
…ion (voidmind-io#30)

* feat: Code Mode — WASM-sandboxed JS execution for MCP tool orchestration (voidmind-io#30)

Add Code Mode: LLMs write JavaScript that orchestrates multiple MCP tool
calls in a single execution, reducing token usage by 30-80%. Scripts run
in a QuickJS/WASM sandbox (fastschema/qjs + Wazero) embedded in VoidLLM.

Three new built-in MCP tools:
- list_servers: discover available MCP servers
- search_tools: find tools by keyword across servers
- execute_code: run JS with MCP tools as async functions

Runtime: pool of QJS runtimes (default 8), fresh runtime per execution,
tool schema cache with lazy fetch, console capture in results.

Configurable via voidllm.yaml (disabled by default):
  mcp.code_mode.enabled, pool_size, memory_limit_mb, timeout, max_tool_calls

Also fixes session re-init double-check in MCP proxy.

* feat: Code Mode Phase 3 — blocklist, refresh, toggle, MCP server split (voidmind-io#31)

Split built-in MCP into two servers:
- /api/v1/mcp — Code Mode (list_servers, search_tools, execute_code)
- /api/v1/mcp/voidllm — Management (list_models, get_usage, etc.)
- /api/v1/mcp/:alias — External MCP server proxy

Per-tool blocklist for Code Mode:
- Migration 0005: mcp_tool_blocklist table
- CRUD API: GET/POST/DELETE /mcp-servers/:id/blocklist
- Defense in depth: filtered before sandbox injection + checked in ToolCaller
- Blocklist also applied to search_tools and list_servers tool counts

Tool refresh endpoint:
- POST /mcp-servers/:id/refresh-tools with 60s cooldown

Admin controls:
- code_mode_enabled toggle in API response and PATCH
- UI: Code Mode toggle column, expanded row with blocklist management

Shared MCP handler helper eliminates POST/SSE handler duplication.

* feat: Code Mode Phase 4 — Proxy pattern, SSE upstream, execution history, TypeScript types (voidmind-io#32)

JS Proxy pattern replaces static preamble generator:
- Single __callTool dispatch via ES6 Proxy interception
- Any tool name characters supported, preamble is O(1) in tool count

SSE upstream transport support:
- Auto-detect Streamable HTTP vs deprecated SSE protocol
- Lazy detection with sync.Once, origin validation on endpoints

Execution history:
- Migration 0006: code_mode_execution_id on mcp_tool_calls
- UUIDv7 per execute_code call groups all tool calls

Dynamic TypeScript types in execute_code description:
- GenerateToolTypeDefs converts cached tool schemas to TS declarations
- OnToolsListHook injects types at tools/list time

Bug fixes:
- MCP access control enforced in all Code Mode closures for global servers
- ToolCache fetcher resolves servers across all scopes
- Frontend blocklist DELETE matches backend query parameter API

* feat: persistent tool cache, SSE detection, tools list UI with block buttons (voidmind-io#33)

Persistent tool cache:
- Migration 0007: mcp_server_tools table for DB-backed tool schemas
- Startup loads from DB (zero HTTP calls, TypeScript types immediately available)
- 24h background refresh keeps schemas current
- Write-through on every fetch (RefreshServer, GetTools)
- DB entries marked stale on load so they refresh within maxAge

SSE transport detection:
- Servers using deprecated SSE protocol auto-deactivated at startup
- Clear error message: "server uses deprecated SSE transport"
- Test connection also detects and deactivates SSE servers

Tools list UI:
- GET /mcp-servers/:id/tools endpoint returns cached tools with blocked status
- Expanded row shows all tools with Block/Unblock buttons
- Block buttons work for YAML-sourced servers (blocklist is independent of source)
- Plug icon centered in sidebar and MCP servers page

Also fixes:
- ToolStore.Delete uses server ID (not alias) to avoid soft-delete lookup failure
- Corrupt JSON schemas skipped on DB load instead of serving empty schemas

* ci: lower patch coverage target to 50%

* refactor: extract Code Mode service from app.go + add 46 tests

Extract 3 closures (ExecuteCode, ListAccessibleMCPServers, SearchMCPTools)
from app.go into codeModeService in code_mode.go. Shared accessibleServers
helper eliminates duplicated server-listing + access-check logic.

New tests:
- code_mode_test.go: 21 tests (mock DB, real WASM executor)
- mcp_tool_blocklist_test.go: 11 tests (CRUD, conflicts, isolation)
- mcp_server_tools_test.go: 14 tests (upsert, replace, active filter)

app.go reduced by ~400 lines.

* test: add 13 handler tests for blocklist, refresh, and tools list endpoints

* docs: add Code Mode section to README with config, limitations, and IDE setup

* test: add 17 tests for CallMCPTool and dbToolStore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant