MCP Tools Reference

Your connected AI client calls these operations when you ask it to work with ThinkForge. You do not need to write requests yourself. Tell it the project, task, and whether it may change files.

Read the project's rules first

get_project_instructions reads the root THINKFORGE.md. The client should call it before other work in that project.

set_project_instructions updates that file with a check against the current content hash. Restart ThinkForge after an instruction change; the running app continues using its cached copy.

Find project information

  • list_projects shows available project names.
  • hybrid_search finds text by words and meaning. It can still use words when meaning-based search is unavailable.
  • semantic_search searches by meaning and needs local semantic search to be available.
  • search_all_projects finds information across projects.
  • list_tags shows a project's tags.
  • tag_search finds documents carrying the requested tags.

A project operation normally uses the active project. The client can name another project explicitly.

Search returns relevant excerpts. For a complete answer or an edit, ask the client to read the whole document.

Read a complete document

get_document_by_path reads the current text file and supplies the content hash needed for an update or move.

get_memory reads a document found through project search. Ask for the current file by path when the client is preparing to change it.

Files larger than 200 KB cannot be read in full through the path-reading operation. Use search to find their relevant sections. The client should not replace a large document using only an excerpt.

Create, revise, or move a file

  • save_artifact creates one new file.
  • save_artifacts creates several new files.
  • update_document replaces the complete text of an existing file.
  • move_document moves or renames a document inside the same project.

Name the destination project and folder when asking for a new file. New files otherwise go to the project's _captured folder. If a filename is already taken, saving a new artifact creates a numbered filename; it does not revise the existing document.

For a revision, the client must read the current file and use its content hash. A stale hash or open document is refused. The client should resolve the conflict and read again. A move cannot overwrite an existing destination.

After a write, the client should read back the file and check the indexing result. A file can be saved even when indexing fails. An image or other binary file can be saved without becoming searchable text.

Successful MCP saves can appear in Recents with ThinkForge MCP as the save source. Completed document operations can also appear in AI Activity. Those views help locate the work; they are not a complete history of everything the client read or did.

index_document refreshes one supported project file.

reconcile_project compares project files with search data. It can refresh changed documents and repair missing search content. It does not guess whether a missing file was deleted or moved. Uncertain missing entries are kept, and new files may wait until that uncertainty is resolved.

Use ThinkForge or move_document for a known move. A successful reconciliation response does not prove that every new file was indexed. If something is still missing, check the file and try indexing it directly.

get_statistics reports search-index status. Incomplete semantic coverage can mean indexing is still working or that some documents could not be processed.

Work on an open Project Map

  • mindmap_get_context reads the selected node and nearby map context.
  • mindmap_find_nodes finds nodes by title.
  • mindmap_search_nodes finds nodes by meaning.
  • mindmap_apply_patch applies supported node and relationship changes.

Keep the intended map active. The client uses the map and node identifiers returned by ThinkForge and reads fresh context before changing it. A stale revision is refused. Deleting nodes or branches asks for confirmation in ThinkForge.

Save the map when newly changed nodes are missing from search. These operations change the map; they do not run Project Map Tool Agents.

Resolve a failed request

  • ThinkForge is unreachable: start the desktop app and reconnect the client.
  • Project not found: ask the client to list projects and use the exact name.
  • Project search is not initialized: open the project and wait for search to finish initializing.
  • Document is open: finish or close it in ThinkForge, then ask the client to read again.
  • Content or revision conflict: ask the client to read the latest file or map and reconsider the change.
  • Saved but indexing failed: check the saved file before retrying creation, then refresh its index.

ThinkForge MCP does not currently list or run user-created Tools or automations. See Running Tools and Running Automations.