Graphtia documentation · workflow
Connect MiniMax Code to Graphtia
Connect MiniMax Code at user and registered-project scope, then verify access to the intended workspace.
- Configured compatibility
- MiniMax Code 3.1.4–3.x
- Configuration scope
- User or project
- After connecting
- Open the connected project
What the integration manages
Explorer has a dedicated adapter for MiniMax Code. It maintains Graphtia’s own MCP registration and guidance while preserving unrelated client settings. The adapter targets MiniMax Code 3.1.4 up to, but not including, 4.0; detection and live verification remain separate checks.
Connect the intended workspace
Open the registered, indexed workspace in Explorer.
Open Settings → AI agents and select MiniMax Code.
Review the supported user and project configuration scopes before connecting.
Review the workspace access request in Explorer and choose its duration.
Open the connected project in MiniMax, then use Test connection in Explorer.
User registration makes the Graphtia server visible in MiniMax settings. Project registration supplies the selected workspace context for queries. Other registered workspaces still require their ordinary permission checks. A visible server entry alone does not prove an authorized project query.
Verify a real question
Ask MiniMax to locate a named symbol in the selected workspace and return its source evidence and revision. Check that the result belongs to the intended root. If access is requested or selection is ambiguous, complete that choice in Explorer before retrying.
Repair, reconnect or disconnect
Use Repair for the Graphtia-owned configuration when Explorer reports a mismatch. Start a fresh client session after connection changes. Disconnect removes Graphtia-owned entries and guidance; it does not remove unrelated MCP servers. If the native surface is unsupported, use Universal MCP only if that client can run a local stdio server.
Privacy and permissions
Structural queries do not edit your repository or index. Requested source context can be sent to the external client under its own data settings. Review those settings before connecting; workspace permission and the optional local recovery cache have separate controls.
Workspace access and persistent permissions