Connect another agent with Universal MCP

When to use Universal MCP

Use this path when your coding agent can start a local MCP server over stdio but does not have a dedicated Graphtia adapter. The client must support a command, arguments and the standard MCP initialization handshake.

Locate the packaged server and project library

1. Install and open Graphtia Explorer.

2. Register the workspace and complete its index.

3. Locate the packaged graphtia-mcp executable in the Explorer installation.

4. Locate Explorer projects.json in the Explorer application data directory.

5. Choose a stable, lowercase identifier for the client.

Server command

graphtia-mcp[.exe] --library <Explorer projects.json> --client <stable-agent-id> --guidance on

Generic local-server shape

{
  "mcpServers": {
    "graphtia": {
      "command": "<absolute path to graphtia-mcp.exe>",
      "args": [
        "--library", "<absolute path to Explorer projects.json>",
        "--client", "<stable-agent-id>",
        "--guidance", "on"
      ]
    }
  }
}

Map this shape to the local stdio server fields used by your client. Do not place the project library contents, tokens or secrets in the agent prompt.

Initialize and approve the workspace

1. Restart the client and confirm that it initializes the Graphtia MCP server.

2. Ask a narrow structural question about a registered workspace.

3. If Graphtia returns AGENT_IDENTITY_REQUIRED, retry the same focused tool with agent_handshake containing agent, client and version.

4. Approve the read-only workspace request in Explorer.

5. Retry the original focused request and confirm the project and revision in the response.

Safe operating boundary

• The identity handshake identifies the client; it never grants workspace access.

• The server exposes read-only structural and documentation tools.

• Approval is visible in Explorer and scoped to a registered workspace.

• The universal connection does not give Graphtia control over the host application.

Native and Universal MCP compared

Native integration

• Automatic detection and version checks.

• Guided connection and host-specific configuration.

• Connection health, verification and Repair in Explorer.

• Managed workspace handshake and Graphtia-owned guidance.

Universal MCP

• Manual local stdio configuration in the third-party client.

• The same Graphtia MCP code-intelligence surface where the client is compatible.

• Workspace identity and approval still remain visible in Explorer.

• Reload, health and configuration UX depend on the third-party host.

Privacy and external providers

Graphtia maintains its code-intelligence index locally. A connected external agent can receive the structural information you request through MCP, and that provider may process it according to its own terms, account settings and data controls. Review those controls before connecting.