Nixpacks

Nixpacks Configuration File (nixpacks.toml)

Projects can override or extend the auto-detected build plan by committing a `nixpacks.toml` (or `nixpacks.json`) file at the root of the repository. The configuration file mirrors the build-plan structure with top-level `providers`, `buildImage`, `variables`, and `staticAssets`, a `[phases.]` table for each phase carrying `cmds`, `nixPkgs`, `nixLibs`, `aptPkgs`, `dependsOn`, `cacheDirectories`, `onlyIncludeFiles`, and `paths`, and a `[start]` table for `cmd`, `runImage`, and runtime-only file inclusion. The `"..."` token can be used inside array fields to extend rather than replace provider-supplied values.

GitHub

Documentation

📖
Documentation
https://nixpacks.com/docs/configuration/file

Other Resources

🔗
Reference
https://nixpacks.com/docs/configuration/environment

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/configuration-file"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: nixpacks:configuration-file
name: Nixpacks Configuration File (nixpacks.toml)
description: Projects can override or extend the auto-detected build plan by committing a `nixpacks.toml`
  (or `nixpacks.json`) file at the root of the repository. The configuration file mirrors the build-plan
  structure with top-level `providers`, `buildImage`, `variables`, and `staticAssets`, a `[phases.<name>]`
  table for each phase carrying `cmds`, `nixPkgs`, `nixLibs`, `aptPkgs`, `dependsOn`, `cacheDirectories`,
  `onlyIncludeFiles`, and `paths`, and a `[start]` table for `cmd`, `runImage`, and runtime-only file
  inclusion. The `"..."` token can be used inside array fields to extend rather than replace provider-supplied
  values.
humanURL: https://nixpacks.com/docs/configuration/file
tags:
- Configuration
- TOML
- Phases
- Customization
properties:
- type: Documentation
  url: https://nixpacks.com/docs/configuration/file
- type: Reference
  url: https://nixpacks.com/docs/configuration/environment