Creating Glaido MCP Servers

What this produces

A self-contained folder that the Glaido desktop app can import as a local tool. The folder always contains an mcp.json (the file Glaido reads on import) plus the server code, its dependencies, and environment setup. After import, the server's tools become available to Glaido's agent.

Glaido runs these servers as local processes over stdio. That focus drives every choice below: the server is launched from disk by an absolute path, it talks MCP over stdin/stdout, and its secrets live in a local .env next to the code.

The user never needs to know anything about Glaido's internals - only how to import the folder and set their keys. Keep your explanations at that level.

Step 0 - Decide: reuse or build?