fix(plugin): revert .mcp.json to HTTP transport#143
Conversation
The command-based config requires the engram binary installed, which isn't distributed yet. Revert to HTTP transport until GitHub Release binaries are set up.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
ОбзорКонфигурация engram MCP переведена с локального выполнения команды на HTTP-интеграцию. Вместо передачи токена через переменные окружения, теперь используется авторизация Bearer в HTTP-заголовках. Изменения
Оценка трудозатрат при проверке🎯 1 (Trivial) | ⏱️ ~3 minutes Стихотворение
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Required for marketplace to detect the .mcp.json revert from PR #143.
Required for marketplace to detect the .mcp.json revert from PR #143. Co-authored-by: Kirill Turanskiy <thebtf@users.noreply.github.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the engram MCP server configuration in .mcp.json, transitioning from a local command execution model to an HTTP-based service. The configuration now specifies an HTTP type, a target URL, and an Authorization header using a bearer token. I have no feedback to provide as there were no review comments.
1 participant
Summary
Reverts .mcp.json from
command: "engram"back totype: "http".The stdio proxy binary isn't distributed via the plugin yet — users who update
the plugin get a broken MCP connection because
engramcommand isn't found.HTTP transport works without any binary installation.
Next steps
Summary by CodeRabbit
Примечания к выпуску