Skip to content

feat: deploy pipeline to mcp.vultisig.com#5

Merged
RaghavSood merged 1 commit intomainfrom
feat/deploy
Feb 24, 2026
Merged

feat: deploy pipeline to mcp.vultisig.com#5
RaghavSood merged 1 commit intomainfrom
feat/deploy

Conversation

@RaghavSood
Copy link
Collaborator

Summary

  • Adds GitHub Actions deploy workflow that deploys on every push to main
  • Adds scripts/deploy.sh adapted from vultisig/verifier

Server Setup (already done)

  • Server: 129.212.217.161 (Debian 13, Go 1.25.5)
  • DNS: mcp.vultisig.com
  • nginx: reverse proxy on port 443 → localhost:8080, with Let's Encrypt SSL
  • systemd: mcp.service running /usr/local/bin/mcp-server -http :8080
  • env: /opt/mcp/.env with ETH_RPC_URL and COINGECKO_API_KEY

GitHub Secrets (already set)

  • SSH_KEY — deploy key for server access
  • SSH_SERVER — 129.212.217.161
  • SSH_USER — root
  • SSH_PATH — /opt/mcp

Deploy Flow

  1. Push to main triggers workflow
  2. Tests run (go vet + go test)
  3. On success: rsync → go build on server → systemctl restart mcp

Verification

Server is already live and responding:

$ curl -s -X POST https://mcp.vultisig.com/mcp -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{...}}'
{"jsonrpc":"2.0","id":1,"result":{"serverInfo":{"name":"vultisig-mcp","version":"0.1.0"}}}

Test plan

  • Server is running and accessible at https://mcp.vultisig.com
  • SSL certificate is valid (Let's Encrypt, auto-renewal enabled)
  • GitHub secrets configured
  • CI deploy workflow runs on merge

🤖 Generated with Claude Code

Deploy on every push to main via GitHub Actions:
- Tests (vet + go test) run first
- On success, rsync code to server, build, and restart systemd service

Server setup (129.212.217.161):
- nginx reverse proxy with Let's Encrypt SSL on mcp.vultisig.com
- systemd service (mcp.service) running mcp-server -http :8080
- .env with ETH_RPC_URL and COINGECKO_API_KEY

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@RaghavSood RaghavSood merged commit 7d9ee4c into main Feb 24, 2026
1 check passed
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