ϟFORGESTUDIO INTELLIGENCEEarly access

INTEGRATIONS / EXTEND YOUR STUDIO

Connect the tools.
Keep the control.

A model becomes useful when it can work with your files and software. Forge Studio Intelligence brings tool discovery, connection status and approvals into the same workspace.

THE TOOL PATH

01 / DISCOVER

GitHub releases

Browse a repository and choose a compatible package.

Download + verify
02 / CONNECT

MCP tool library

Inspect the server and its available actions.

Approved action
03 / EXECUTE

Your Work chat

The model calls a tool and receives its result.

LOCAL / STDIO

Tools on your machine

Connect a local MCP executable with its startup arguments. Discover its tool names and input schemas. Enable, refresh, disable or remove the connection from the library.

REMOTE / HTTP

Connected services

Use supported MCP HTTP services through Integrations. Remote actions can send data to their service; authentication and compatibility depend on the server.

PACKAGES / GITHUB

From release to executable

Browse release assets, download a Windows package, verify supplied checksums and extract ZIPs. Choose the CLI executable when a tool exposes MCP; a desktop app alone is not an MCP server.

A PDF workflow.
One connected tool.

PDFCraft is an example of extending Forge Studio Intelligence with a separately installed tool. Its MCP connection has been confirmed on the Windows installation; a complete model-driven PDF workflow remains under verification.

01

Install the CLI

Download the appropriate portable package, extract it and select pdfcraft-cli.exe.

02

Inspect the actions

Start its MCP mode, optionally confine it to a PDF folder, and review the discovered catalog.

03

Ask in Work

Give the model a PDF path and a specific task. Inspect the result before trusting or sharing the output.

Access is a decision.

Local tool processes run with your Windows account access. A checksum checks file integrity, not the trustworthiness of the software. Forge Studio Intelligence keeps connection management and action approvals visible.

Local MCP processes are not supported in Forge’s sandbox execution mode. General OAuth setup, arbitrary package installation and server-requested sampling are not automatic. External products retain their own licenses.

FORGE STUDIO INTELLIGENCE / EARLY ACCESS

Bring your next
ambitious idea.

Explore the beta. Tell us what you want to build.

Contact Forge Studio Intelligence