Neptune MCP Server
<p align="center">
<img src="./assets/neptune.svg" alt="Neptune Logo" width="200"/>
</p>
<p align="center">
<em>Give your coding agents DevOps superpowers</em>
</p>
<p align="center">
<img src="./assets/neptune.gif" width="600" alt="Neptune flow" />
</p>
## What is Neptune?
Neptune is an app deployment platform built for AI agents that gives your agents real DevOps abilities. It reads your code, infers the infra it needs, and generates a simple IaC spec you can inspect, approve, and apply. Think: coding agents that can actually ship safely to AWS.
## Deploy Your First App
Follow the steps below and you can deploy your app in minutes.
Install the Neptune MCP server:
```bash
curl -LsSf https://neptune.dev/install.sh | bash
```
**Windows (PowerShell):**
```powershell
irm https://neptune.dev/install.ps1 | iex
```
## Getting Started
For Cursor, go to Cursor Settings -> Tools & MCP -> New MCP Server:
```json
{
"mcpServers": {
"neptune": {
"command": "neptune",
"args": ["mcp"]
}
}
}
```
## Deploy Your App
That's it! Now just tell your agent to deploy your app for you, and Neptune will handle the rest.
## Local Development
To test local changes to the MCP server, update your MCP config to point to your local repo:
```json
{
"mcpServers": {
"neptune": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/neptune-mcp",
"neptune",
"mcp"
]
}
}
}
```
Replace `/path/to/neptune-mcp` with the absolute path to your local clone.
After updating the config, restart Cursor (or reload the MCP server) for changes to take effect.
You can also verify the MCP server starts correctly from the terminal:
```shell
uv run neptune mcp
```
TDQS
Scored across 15 tools
Most tools have distinct purposes, but wait_for_deployment and get_deployment_status are closely related and add_new_resource's name is misleading (it only returns info about resource types, not actually adding). However, descriptions generally clarify the differences.
The majority follow a verb_noun pattern (list_projects, get_logs, delete_project), but some deviate: 'info' and 'login' lack objects, and 'add_new_resource' implies an action different from its actual informational purpose. This mixed convention reduces predictability.
15 tools is at the high end of the ideal range, but each addresses a distinct aspect of cloud deployment and management. A few informational tools (info, get_project_schema, add_new_resource) are somewhat redundant but still marginally useful.
Core project operations (list, deploy, delete, status) and resource operations (provision, bucket, secret, database) are covered, but there is no create_project tool, no secret retrieval, and no resource deletion. These gaps may require workarounds.