feat: enable AI integration with MCP server

[MicBun]

resolves: #1148

Summary by CodeRabbit

• Chores
  • Updated the Postgres container image source to ghcr.io/trufnetwork/postgres-mcp:latest, ensuring alignment with the official registry.
  • Revised AMI test script to use the new image and container name (tn-postgres), updating readiness and connection checks accordingly.
  • Harmonized status messages to reflect the new image and naming.
  • No functional changes expected; improves consistency and reliability across environments.

[coderabbitai]

Walkthrough

Updated Postgres MCP image reference in Docker Compose and aligned the AMI test script with new image, container name, and connection parameters.

Changes

Cohort / File(s)	Summary
Infra compose image update deployments/infra/stacks/docker-compose.template.yml	Changed postgres-mcp image from crystaldba/postgres-mcp:latest to ghcr.io/trufnetwork/postgres-mcp:latest.
AMI test script updates scripts/test-ami.sh	Replaced image refs to ghcr.io/trufnetwork/postgres-mcp:latest; renamed container kwil-postgres → tn-postgres; updated readiness and psql commands (kwild/kwild → postgres/kwild); adjusted echoed messages and simulated pull output.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: simplify AMI deployment and fix overwriting config #1173 — Similar updates to Postgres service naming and image references across compose and AMI/test scripts.
• feat: setup node inside AWS AMI Instance #1172 — Parallel refactors adjusting Postgres image/container names and DB URI usages in related deployment scripts.

Suggested reviewers

• outerlook

Poem

Hop hop, a tag we swap,
From crystal streams to ghcr’s shop.
TN drums, containers thrum,
tn-postgres wakes with steady hum.
I twitch my nose—tests pass, all clear,
Carrots cached, deploy is near! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title suggests a new AI integration feature for the MCP server but the changes only update Docker image references and container names without introducing AI integration, SSE configuration, or related setup.	Please update the title to accurately reflect the scope of changes, for example focusing on updating the postgres-mcp Docker image reference and test script container names.
Linked Issues Check	⚠️ Warning	The changes only adjust Docker image paths and script container names but do not implement any of the acceptance criteria from issue #1148, such as configuring SSE transport, setting up a systemd service, modifying security groups, updating the tn-node-configure script, adding health monitoring, or documenting the SSE endpoint.	Complete the missing objectives from issue #1148 by adding SSE transport configuration, systemd service setup, firewall rules, tn-node-configure enhancements, monitoring and logging, and documentation for the exposed URL.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Out of Scope Changes Check	✅ Passed	All modifications are focused on updating the postgres-mcp image reference and related container names in the Docker compose template and test script, which aligns with the objective of integrating the MCP server with Docker deployments.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch useMCPAmi

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ac5dc78 and cd951de.

📒 Files selected for processing (2)

• deployments/infra/stacks/docker-compose.template.yml (1 hunks)
• scripts/test-ami.sh (3 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-09-19T18:59:51.942Z

Learnt from: outerlook
PR: trufnetwork/node#1168
File: tests/extensions/tn_digest/test_tn_digest.sh:15-15
Timestamp: 2025-09-19T18:59:51.942Z
Learning: In Docker Compose files, service names (like "tn-db:") can remain unchanged even when the underlying image is updated (e.g., from tn-db:local to ghcr.io/trufnetwork/node:local). Service names are internal network identifiers and don't need to match the actual image names.

Applied to files:

• deployments/infra/stacks/docker-compose.template.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: acceptance-test

🔇 Additional comments (3)

deployments/infra/stacks/docker-compose.template.yml (1)

84-84: Image swap looks good

Switching to ghcr.io/trufnetwork/postgres-mcp:latest keeps the compose stack consistent with the new registry layout. No issues spotted on this service definition.

scripts/test-ami.sh (2)

376-409: Test updates align with the new MCP image

The availability probe and the PostgreSQL startup checks now track the GHCR image and tn-postgres container naming, so the AMI verification script remains in sync with the compose stack. Looks solid.

---

458-459: Update workflow messaging stays accurate

Glad to see the simulated update output referencing the new MCP image—keeps operator guidance clear.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[holdex]

Time Submission Status

Member	Status	Time	Action	Last Update
MicBun	✅ Submitted	3h	Update time	Sep 26, 2025, 5:37 PM
@outerlook	❌ Missing	-	⚠️ Submit time	-