Something I shipped recently that I think more developers should know about: the NEXUS AI MCP server.
Here's the practical version of what it enables.
You're building with Claude Code. You finish a feature. Normally you'd commit, push, wait for CI, then go check your deployment platform to see if it worked. Maybe tail logs in a separate tab. Maybe open a DB console if something breaks.
With the NEXUS AI MCP server connected, Claude handles all of that.
Setup takes about 2 minutes. Add this to your Claude Desktop config:
```json
{
"mcpServers": {
"nexus-ai": {
"url": "https://api.zollo.live/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
```
Generate a token at nexusai.run/app/tokens. That's it.
What Claude can now do for you:
Deploy from your repo: "Deploy my main branch to production" → Claude calls nexusai_deploy_source, builds from GitHub, gives you a live URL.
Add a database: "Spin up a Postgres database for this deployment" → Claude calls nexusai_managed_db_create, attaches it, injects the connection string.
Watch for errors: "Are there any errors in my app logs?" → Claude calls nexusai_deploy_logs, reads the output, surfaces anything worth fixing.
Back up before a migration: "Back up the database before I run this migration" → Claude calls nexusai_db_backup, confirms the snapshot is ready, then you proceed.
Roll back if something breaks: "The last deploy broke something, roll it back" → Claude calls nexusai_deploy_rollback, restores the previous version.
Fix a schema issue: "My app is throwing a column not found error, fix it" → Claude reads the log, proposes the DDL fix via nexusai_db_propose_fix, you approve, Claude applies it via nexusai_db_apply_fix.
The loop closes: Claude writes the code and Claude manages the deployment. You stay in the conversation.
NEXUS AI has a free tier (one deployment, no credit card). The MCP server works on the free tier.
Full setup guide: nexusai.run/docs