Connect an assistant to Forge MCP
Authorize the correct Forge account, start with a read, and review supported draft writes before approval.
Forge MCP lets a compatible assistant use the tools and information permitted by your Forge account authority. It is a separate access surface from the Foundry OMS dashboard: connecting an assistant does not automatically enable every commerce action or bypass a module's rollout controls.
Start with a read-only Northgate ESD Packaging task, such as listing project metadata, before asking the assistant to create anything.
Prepare the connection
You need an active Forge-entitled account, the required membership, and an MCP-compatible client that supports the remote connection flow. The account's MCP controls must also allow access.
The remote endpoint is:
https://forge.thevikingstack.com/mcp
Use that exact HTTPS address. Do not append an event-stream path, account identifier, credentials, or a session value. The browser authorization flow supplies the connection authority.
For client-specific controls, use the Forge MCP setup guide. Client menus can change; the important Forge steps are signing in, reviewing consent, and choosing the intended account.
Authorize the intended account
- Add the remote endpoint in your client's MCP or connector settings.
- Start the client's connection or authorization flow.
- Sign in through the browser.
- Read the Forge consent screen.
- Select the intended active account, such as the Northgate demo account when it is available to you.
- Complete consent and return to the client.
- Ask for a small read that confirms the expected account context.
An ordinary account grant remains bound to that account. Selecting a different business in the Forge web interface does not move the grant. To use another account, revoke the grant and connect again for the intended account.
Platform-owner grants are a distinct administrative capability. A verified platform owner sets an authorized account context before customer-data calls. Ordinary account users do not need that workflow, and context handles are private temporary connection data.
Make the first request specific
A useful first instruction is: “List the project metadata available for Northgate ESD Packaging and summarize the project names. Do not create or publish anything.” The returned information should match the account you authorized.
Forge's documented account tools expose project, asset, connection, and AEO metadata. They do not return stored asset bodies or provider secrets. If the assistant cannot read an asset's full content, that can be an intentional boundary rather than a connection failure.
Do not infer broader tool access from a successful connection. Current role, membership, entitlement, and MCP controls are checked on requests, so access can change after a grant was created.
Review draft writes
Supported account writes are bounded project and draft-asset creation for authorized roles. They require client approval and an operation key. Before approving, read the proposed account, project, asset type, and content inputs.
For Northgate, creating a draft FAQ asset should produce a draft in the intended project. It should not be described as publishing the FAQ to the storefront. Review and publication remain separate actions in the appropriate Forge surface.
If an assistant proposes a write outside the supported tools or your authority, clarify the task rather than trying to work around the restriction.
Disconnect or troubleshoot
Open Settings > Connections in Forge to revoke a connected client. You can also disconnect it in the client; revocation in Forge stops the grant even if the client still lists its configuration.
For authorization errors, check the account's active status, entitlement, role, and MCP controls. For stale authorization, repeat the normal sign-in flow. For help, keep the error code and request identifier; do not copy tokens or context handles into a ticket.