Connect a compatible AI client to ThinkForge MCP so it can search your projects, read documents, and save or revise project files. ThinkForge must be running on the same computer.
Connect an AI client
Open ThinkForge's Settings and its MCP section. Use the client setup controls there, or follow Using MCP with AI Clients for manual configuration.
ThinkForge starts its local MCP connection automatically. Clients connect to http://localhost:3001, or use the Fire.exe --mcp-stdio command when they require a stdio connection. If you installed ThinkForge from the Microsoft Store, the command is thinkforge.exe --mcp-stdio.
Automatic configuration creates a .thinkforge.bak backup alongside a client's configuration before the first change. Restart or reconnect the client after setup.
If the client reports that ThinkForge is unreachable, start the desktop app and reconnect. Open the intended project and allow its search index to initialize.
Choose the project
An AI client uses the active project unless it names another project. Tell it which project you want it to work with, especially before saving or changing files.
Clients can list projects and search across projects without changing the desktop's active project. Project search returns excerpts; ask the client to read the complete document before relying on it or revising it.
Give a project standing instructions
Put project guidance in the root file THINKFORGE.md. Ask the client to read it before working in that project.
MCP can update the instructions with a check that prevents overwriting a newer file. ThinkForge caches instructions while running. Restart ThinkForge after creating or changing THINKFORGE.md so new requests receive the new rules.
These instructions guide the AI client. They do not prevent a client from making a mistaken edit, so give it clear scope and review consequential changes.
Save or revise documents
A connected client can create files, read current files, revise text, or move documents inside a project. For an existing document, it must read the current file and use the returned content hash when updating or moving it.
ThinkForge refuses a stale edit, a document open in the desktop app, or a move onto an existing file. The client should read again and resolve the conflict.
Document changes update project search. A successful file save and successful indexing are separate results: if indexing fails, the file may still have been saved.
Work with a Project Map
MCP can read and search nodes in the active Project Map and apply supported changes. Keep the intended map open. The client must use fresh map context before editing; a stale change is refused.
Deleting nodes or branches requires confirmation in ThinkForge. Save the map if search cannot find recent node changes.
For the user workflow, see Project Map.
Current limits
ThinkForge MCP is a local connection. It stops when ThinkForge exits.
It does not currently list or run your user-created Tools or automations. Run those from their desktop placements.
For the available operations and common errors, see MCP Tools Reference.