Beta Status
ThinkForge MCP does not currently expose user-created Agent Tools.
External AI clients cannot discover or execute your tools through MCP.
What ThinkForge MCP Does Provide
The MCP server focuses on project knowledge and safe document operations. Depending on the connected client, available operations include:
- Hybrid and semantic SK Memory search
- Cross-project search
- Project listing and project instructions
- Full document reads by project-relative path
- Hash-safe document updates and moves
- Artifact saving, including text and binary content
- Tags, memory retrieval, statistics, indexing, and project reconciliation
- Reading the active Mind Map context and applying revision-safe child-node additions
See the MCP section for setup and the current tool reference.
Transport
ThinkForge MCP is reached by supported clients through the configured MCP connection, including the stdio bridge where applicable. This is separate from the Chrome extension's connection on localhost:19222.
Mind Map MCP operations work with the active selected map. They are deterministic document operations and do not discover or run the native Mind Map Tool Agents.
Planned General Integration
Discovering, inspecting, and running Agent Tools through MCP is designed but not shipped. Do not plan beta workflows around it.
Current Alternatives
To run a user-created tool today, use:
- The desktop Tools page
- Power Strip
- The Ribbon
- The Mobile Dashboard
- An automation in the Automations tab
Use MCP for knowledge access and document changes, not for tool execution.
Mind Map also offers Work with Codex as an alternative to Run Action. The Codex path uses the deterministic Mind Map MCP operations; it does not run the selected native Tool Agent. Only one of those two execution paths can work on the map at a time.