Building a local MCP server inside a Rust desktop app

Description and use

An embedded local MCP server in AssetHoard enables safe, real-time asset manipulation via AI assistants using HTTP and a shared API, preventing database corruption and keeping the UI in sync.

Problem

Integrating a local MCP server into a desktop asset manager without corrupting the SQLite database or losing UI sync.

Outcome

The embedded MCP server allows real-time, safe asset manipulation via AI assistants while maintaining database integrity and UI responsiveness.

Workflow

• Run AssetHoard with MCP server enabled via Settings toggle
• MCP server listens on 127.0.0.1:47823 with a bearer token
• Client (Claude, VS Code, etc.) sends HTTP requests with token header
• Server forwards requests to internal library API, performing validation, audit logging, and undo stack entries
• Responses include text results, thumbnails, deep links, and error messages
• Client displays results and updates UI in real time

Evidence

The server runs inside AssetHoard and only answers while the app is open.

Source

MCP never touches the database

Source

The port is fixed at 47823 by default. It is configurable, but the app never picks another one on its own if it is busy.

Source