Model Context Protocol (MCP)
Connect AI assistants to your Nextune applications, databases, and custom domains.
Nextune CLI includes a Model Context Protocol (MCP) server (nextune mcp) that enables AI coding tools (such as Cursor and Claude Desktop) to view and manage your deployments, databases, and domains.
Quick start
Run the MCP server directly via stdin/stdout:
nextune mcpBy default, nextune mcp automatically uses your active logged-in session (~/.config/nextune/config.yaml).
Alternatively, pass a dedicated scoped API Key:
nextune mcp --api-key SK-your-api-key-hereAdding to Cursor
Add Nextune as an MCP server in .cursor/mcp.json or in your Cursor settings:
{
"mcpServers": {
"nextune": {
"command": "nextune",
"args": ["mcp"],
"env": {
"NEXTUNE_API_KEY": "SK-your-api-key-here"
}
}
}
}If you are already logged in via nextune login, you can omit the env section:
{
"mcpServers": {
"nextune": {
"command": "nextune",
"args": ["mcp"]
}
}
}Adding to Claude Desktop
Add Nextune to claude_desktop_config.json:
{
"mcpServers": {
"nextune": {
"command": "nextune",
"args": ["mcp"],
"env": {
"NEXTUNE_API_KEY": "SK-your-api-key-here"
}
}
}
}Available tools
Once connected, your AI assistant dynamically receives the list of available tools based on your active session or API key permissions:
| Tool | Description |
|---|---|
whoami | Get authenticated user and active workspace context |
list_applications | List all deployed applications in the active workspace |
get_application_status | Get status, details, and configuration for an application |
get_deployment_logs | Fetch recent build and deployment logs for an application |
deploy_application | Trigger a build or redeploy for an application |
restart_application | Restart a running application service |
stop_application | Stop a running application service |
start_application | Start a stopped application service |
list_databases | List managed databases (PostgreSQL, Redis, MariaDB) |
get_database | Get detailed status and host information for a database |
restart_database | Restart a managed database instance |
list_domains | List custom domains attached to workspace applications |
search_domain | Search domain availability and pricing for a domain or keyword |
Permissions & RBAC Scope Filtering
Tools are automatically filtered at discovery (tools/list). An API key or user session only discovers tools they have permission to access.
For example:
- An API key with
applications:readwill only see read tools (list_applications,get_application_status,get_deployment_logs). - Management operations (
deploy_application,restart_application,stop_application) require write permissions (applications:write).