> ## Documentation Index
> Fetch the complete documentation index at: https://trueforge.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Initial Setup

> Configure models, MCP servers, skills, and a sandbox provider once — then reuse them across every agent.

Before you build agents, configure the shared resources TrueForge orchestrates. You do this once in **Settings**; agents then pick from what you have connected.

| Resource | Settings page | Purpose | Shipped catalog |
| - | - | - | - |
| [Models](/models) | **Settings → Models** | Provider credentials and available model IDs | [`model-catalog.yaml`](https://github.com/truefoundry/trueforge/blob/main/packages/trueforge/catalog/model-catalog.yaml) |
| [MCP servers](/mcp-servers) | **Settings → Connectors** | Tools and data from external systems | [`mcp-catalog.yaml`](https://github.com/truefoundry/trueforge/blob/main/packages/trueforge/catalog/mcp-catalog.yaml) |
| [Skills](/skills) | **Settings → Skills** | Git-backed procedures the agent can load on demand | [`skill-catalog.yaml`](https://github.com/truefoundry/trueforge/blob/main/packages/trueforge/catalog/skill-catalog.yaml) |
| [Sandbox](/sandbox) | **Settings → Sandbox providers** | Isolated compute for code, files, and skill execution | [`sandbox-catalog.yaml`](https://github.com/truefoundry/trueforge/blob/main/packages/trueforge/catalog/sandbox-catalog.yaml) |

## What is supported out of the box

Each Settings page is backed by its **shipped catalog** — a YAML file in the TrueForge server (linked above) that lists the presets the UI can offer.

Catalogs are discovery lists only. Choosing a preset in the UI asks you for credentials (API key, OAuth, and so on); TrueForge stores the configured resource in its database and then they are used in the agent configuration.

<Note>If you remove an entry from the catalog after configuring it in the UI, it will still be available for selection in the agent configuration.</Note>

You can also add entries that are **not** in a catalog — for example a custom OpenAI-compatible model endpoint, or an MCP server at any URL.

## Changing what the UI offers

If you self-host TrueForge and want a different preset list (add internal MCP servers, trim unused models, ship company skills), point the server at your own YAML files:

| Env var | Overrides |
| - | - |
| `MODEL_CATALOG_PATH` | Model provider presets |
| `MCP_CATALOG_PATH` | MCP server presets |
| `SKILL_CATALOG_PATH` | Skill presets |
| `SANDBOX_CATALOG_PATH` | Sandbox provider presets |

When unset, TrueForge uses the catalogs shipped with the server.

## Who can change Settings

With [login / OIDC](/authentication/overview) enabled, only users with the **admin** role can open and change Settings. Everyone can still chat and use agents. Without OIDC (typical local mode), Settings are open to whoever can reach the server.

## Next step

Once models (and any connectors, skills, or sandbox you need) are configured, [create an agent](/create-agent/overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.