ExaltByte MCP Server
Allows deploying Docker images as applications or managed services, including setting environment variables, attaching custom domains, and scaling.
Enables deploying applications from GitHub repositories, browsing connected repos, and triggering redeploys.
Enables deploying applications from GitLab repositories, browsing connected repos, and triggering redeploys.
Provides tools for creating and managing MongoDB databases, including listing, resizing, backups, and health monitoring.
Provides tools for creating and managing MySQL databases, including read replicas, backups, and health monitoring.
Supports deploying Next.js applications from GitHub/GitLab repositories with automatic framework detection via Nixpacks.
Provides comprehensive PostgreSQL database management, including creation, resizing, read replicas, PgBouncer connection pooling, backups, and health monitoring.
Allows creating and managing Redis databases and deploying Redis services as managed services.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ExaltByte MCP Serverdeploy my app from GitHub repo owner/my-app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ExaltByte MCP Server
Deploy apps, manage databases, and operate your entire cloud infrastructure from AI assistants like Claude Code — no dashboard required.
What is this?
An MCP (Model Context Protocol) server that connects Claude Code, Claude Desktop, and other MCP-compatible AI assistants directly to the ExaltByte platform API. You describe what you want in natural language, and the AI handles the rest.
You: "Deploy my Next.js app from github bimapanduw/my-app with a Postgres database"
Claude: → deploys the app via deploy_app
→ creates a PostgreSQL database via create_database
→ sets DATABASE_URL on the app via update_env_vars
→ returns the live URLQuick Start
1. Get your API key
Go to Settings > API Keys in the ExaltByte Dashboard and create a new key. Copy the key and your Organization ID.
2. Add to Claude Code
Add to your ~/.claude/settings.json:
{
"mcpServers": {
"exaltbyte": {
"command": "npx",
"args": ["-y", "@exaltbyte/mcp-server"],
"env": {
"EXALTBYTE_API_KEY": "dbaas_your_api_key_here",
"EXALTBYTE_ORG_ID": "your-org-id"
}
}
}
}3. Start using it
claude "deploy my app from github owner/repo"
claude "create a postgres 16 database called mydb"
claude "what's my current billing usage?"Setup for other clients
Add to your claude_desktop_config.json:
{
"mcpServers": {
"exaltbyte": {
"command": "npx",
"args": ["-y", "@exaltbyte/mcp-server"],
"env": {
"EXALTBYTE_API_KEY": "dbaas_your_api_key_here",
"EXALTBYTE_ORG_ID": "your-org-id"
}
}
}
}Config file location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add to .vscode/settings.json in your project:
{
"claude-code.mcpServers": {
"exaltbyte": {
"command": "npx",
"args": ["-y", "@exaltbyte/mcp-server"],
"env": {
"EXALTBYTE_API_KEY": "dbaas_your_api_key_here",
"EXALTBYTE_ORG_ID": "your-org-id"
}
}
}
}Environment Variables
Variable | Required | Description |
| Yes | Your API key (starts with |
| Yes | Your organization ID |
| No | API base URL (default: |
Available Tools (41)
Apps
Tool | Description |
| Deploy from GitHub/GitLab repo or Docker image. Auto-detects framework with Nixpacks. |
| List all deployed applications. |
| Get app details: URL, build info, status. |
| Start, stop, restart, or redeploy an app. |
| Permanently delete an app. |
| Set environment variables (triggers redeploy). |
| Read current environment variables. |
| Change branch, build path, port, or Docker image. |
| Attach a custom domain. |
| Get recent container logs. |
| Get build/deploy logs for a specific deployment. |
App Scaling
Tool | Description |
| Add/remove nodes or resize a node for horizontal/vertical scaling. |
| List all nodes for a horizontally-scaled app. |
Databases
Tool | Description |
| Create PostgreSQL, MySQL, Redis, or MongoDB. |
| List all databases. |
| Get details + connection string (includes PgBouncer pooler for Postgres). |
| Start, stop, or restart a database. |
| Change instance size (restarts the database). |
| Permanently delete a database. |
| Get recent container logs. |
| CPU, memory, disk, connections, cache hit ratio. |
| List supported engines and versions. |
Backups
Tool | Description |
| List all backups for a database. |
| Create a manual backup. |
| Restore from a specific backup. |
| Enable/disable automated daily backups. |
Replicas
Tool | Description |
| List read replicas (PostgreSQL/MySQL). |
| Create a new read replica. |
| Delete a read replica. |
Services
Tool | Description |
| Deploy a Docker image as a managed service. |
| List all services. |
| Get service details. |
| Start, stop, restart, or redeploy a service. |
| Permanently delete a service. |
| Set environment variables (triggers redeploy). |
| Attach a custom domain. |
| Get recent container logs. |
| Browse available pre-configured images (Redis, Memcached, etc). |
Billing & Pricing
Tool | Description |
| Balance, burn rate, estimated days left, per-resource cost breakdown. |
| Available sizes with CPU, memory, and pricing. |
Discovery
Tool | Description |
| Browse GitHub/GitLab repos connected to the org. |
Example Prompts
Deploy a full-stack app:
"Deploy my Next.js app from github myuser/my-app on the main branch, create a postgres 16 database called myapp-db, and set the DATABASE_URL env var on the app"
Check costs:
"What's my current usage and how many days of balance do I have left?"
Scale up:
"Resize my production database to large and add another node to my web app"
Manage backups:
"Enable daily backups on my postgres database and trigger one now"
Debug issues:
"Show me the logs for my api-server app and check the database health"
Deploy a Redis cache:
"Deploy a Redis 7 service called my-cache on a micro instance"
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build
npm run build
# Run production build
npm startHow it works
The MCP server runs as a local stdio process. When an MCP-compatible AI assistant (like Claude) needs to interact with ExaltByte, it calls the appropriate tool with structured parameters. The server translates these into ExaltByte API calls and returns formatted results.
User prompt → Claude → MCP tool call → ExaltByte API → Response → Claude → UserAll communication happens over stdin/stdout using the Model Context Protocol. No HTTP server is needed.
License
MIT
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bekatechnology/exaltbyte-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server