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

# Choose a Forge interface

> Choose Console, HTTP API v3, or MCP by caller and task.

Forge exposes the same platform through interfaces designed for different callers. Choose by who
acts and where the client runs.

| Interface | Best for | Credential | Important constraint |
| - | - | - | - |
| Forge Console | People authoring and operating | Interactive person session | Human UI, not an automation contract |
| HTTP API v3 | Services, scripts, and products | External App OAuth token; supported person keys where allowed | Implement idempotency, paging, and error handling |
| Hosted MCP | AI hosts acting for a person | Interactive OAuth or Personal key | Model-oriented default surface; not every API operation is a named tool |
| Local MCP stdio | AI hosts acting as an External App | Client credentials, or a Personal key | You operate the local process and secret environment |

## Choose Console

Use Console for human review, exploration, workflow authoring, approvals, incident response, and
configuration. UI labels and routes can evolve; software should use the HTTP or MCP contracts.

Start with [Console documentation](https://docs.gloo.com/forge/console.md).

## Choose HTTP API v3

Use API v3 for deterministic integrations that own request construction and error handling. The
generated operation reference remains organized by the underlying v2 operation identity; v3 maps
those operations to resource-oriented paths without changing their authorization or business logic.

Start with the [Raw HTTP quickstart](https://docs.gloo.com/forge/quickstart.md) and the [API reference](https://docs.gloo.com/forge/reference.md).

## Choose MCP

Use MCP when an AI host should discover and perform Forge tasks. The default listing is deliberately
bounded. Core tools cover common jobs; search and describe operations expose the wider catalog, and
separate read/write callers preserve host confirmation behavior.

Start with [MCP host quickstart](https://docs.gloo.com/forge/quickstart/mcp-host.md).

## Combine interfaces deliberately

A common pattern is Console for setup and incident response, HTTP for the production integration,
and MCP for ad hoc operator assistance. These callers may use different identities and therefore
see different resources. Test each credential and scope independently.

## Console and the HTTP API share one platform

Forge Console and HTTP API v3 reach the same platform state and the same domain services. They
serve different callers, so their contracts differ.

| | Forge Console | HTTP API v3 |
| - | - | - |
| Caller | A person authoring or operating work | A service, script, or application |
| Identity | The signed-in person | The credential admitted by the operation |
| Interaction | Interactive views, controls, and live updates | Documented requests and responses |
| Contract | Console's supported screens and actions | The operation's published schema |

### How Console connects

Console keeps run state, approvals, and other views current through live subscriptions. It submits
actions with the signed-in person's identity, and the applicable permissions and runtime
governance apply.

### How software connects

New integrations call the documented `/api/v3/*` operations with the credential each operation
admits. Forge authenticates the caller, validates the request, delegates to the owning service, and
returns the published response shape. For updates, use supported [webhook events](https://docs.gloo.com/forge/run/webhooks.md)
or read operation status through the API. Console's subscriptions are not an external
subscription contract.

Sharing a backend does not make Console view models and HTTP response shapes interchangeable.
Build external integrations against the published API contract. Authorization applies on each
path, and the applicable Trust Fabric controls govern the work it invokes. See the
[system overview](https://docs.gloo.com/forge/architecture/system-overview.md) for the wider execution model.

## Related

* [Quickstart](https://docs.gloo.com/forge/quickstart.md): the Console and raw HTTP path.
* [MCP host quickstart](https://docs.gloo.com/forge/quickstart/mcp-host.md): connect an AI host to Forge.
* [Access and credentials](https://docs.gloo.com/forge/get-started/credentials-and-access.md): which credential each interface uses.


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