Lineai MCP server

lineai-mcp-server

An MCP Server to utilize Lineai's rich software dependency data in your AI programming assistant.

Components

Tools

The server implements eight tools: two impact tools plus six graph tools backed by the Lineai graph HTTP API.

Code Analysis Tools

• lineai-method-impact: Pulls an impact assessment from the Lineai server's APIs for your code.
• Takes the given "method" that you're working on and its associated "class".
• lineai-database-impact: Analyzes impacts between code and database entities.
• Takes the database entity type (column, table, or view) and its name.

Graph API tools

These call POST / GET endpoints under /api/ai-retrieval/graph/ on the same host as LINEAISERVERHOST, using the same session auth as other MCP tools. If graph routes are not deployed, the server returns a clear “graph not available” style message (often after HTTP 404).

• lineai-graph-capabilities: GET — discover supported relationship types, limits, and flags for the workspace materialized view (materializedViewId defaults from LINEAIWORKSPACENAME like other tools).
• lineai-graph-search: Search nodes by text query / q and/or identityprefix; optional scanspace, limit, etc.
• lineai-graph-impact: Dependency / blast-radius style traversal from seednodeids.
• lineai-graph-path-explain: Shortest-path style explanation between fromnodeid and tonodeid.
• lineai-graph-validate-change-scope: Heuristic checklist / risk summary for a proposed change given seed nodes and proposedchangesummary.
• lineai-graph-owners: Resolve a node by nodeid or identityprefix and surface property fields whose names contain "owner".

Tool arguments accept snakecase aliases (for example materializedviewid, seednodeids) where noted in the MCP schema; request bodies sent to Lineai use camelCase** JSON keys.

Install

Pre Requisites

The MCP server relies upon Astral UV to run, please install

MacOS Workaround for uvx

There is a known issue with uvx on MacOS where the Lineai MCP server may fail to launch in certain IDEs (such as Cursor), resulting in errors like: See issue #11

Failed to connect client closed

This appears to be a problem with Astral uvx running on MacOS. The following can be used as a workaround:

1. Clone this project locally.
2. Configure your mcp.json to use uv instead of uvx. For example:

{
  "mcpServers": {
    "lineai-mcp-server": {
      "type": "stdio",
      "command": "<PATH_TO_UV>/uv",
      "args": [
        "--directory",
        "<PATH_TO_THIS_REPO>/lineai-mcp-server-main",
        "run",
        "lineai-mcp-server"
      ],
      "env": {
        "LINEAI_SERVER_HOST": "<url to the server e.g. https://myco.app.lineai.net>",
        "LINEAI_USERNAME": "<my username>",
        "LINEAI_PASSWORD": "<my password>",
        "LINEAI_WORKSPACE_NAME": "<my workspace>",
        "LINEAI_DEBUG_MODE": "true"
      }
    }
  }
}

1. Restart Cursor.
2. Ensure the Cursor Global Rule for Lineai is in place.
3. Open the MCP tab in Cursor and refresh the lineai-mcp-server.
4. Ask Cursor to make a code change in an existing class. The MCP server should now run the impact analysis successfully.

Configuration for Different IDEs

Visual Studio Code Configuration

To configure this MCP server in VS Code:

1. First, ensure you have GitHub Copilot agent mode enabled in VS Code.

1. Create a .vscode/mcp.json file in your workspace with the following configuration:

Shortened. The full README is on GitHub.