Back
NOVA MCP // NOVA MCP API & Keys
NOVA MCP API & Keys
Docs › NOVA MCP
API & keys
Every tool is also a plain HTTPS call, for scripts and CI. Make a key on the NOVA MCP page in your account, choosing what it may do. It is shown once.
curl -X POST https://runnova.ai/api/mcp/v1/plan_and_credits \ -H "Authorization: Bearer $NOVA_MCP_KEY"
curl -X POST https://runnova.ai/api/mcp/v1/deploy \
-H "Authorization: Bearer $NOVA_MCP_KEY" \
-H "Content-Type: application/json" \
-d '{"project_id": "your-project-id", "confirm": true}'
# then poll
curl -X POST https://runnova.ai/api/mcp/v1/job_status \
-H "Authorization: Bearer $NOVA_MCP_KEY" -d '{"job_id": "..."}'List the tools
GET /api/mcp/v1/tools: names, inputs, the access each needs, and which ask first.Call a tool
POST /api/mcp/v1/<tool> with its arguments as JSON.Limits60 calls a minute per account, and your plan's jobs a day.
In CI, confirm: true is how you say yes in advance: only put it in a pipeline you mean to deploy from.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.