Lets AI coding assistants query software dependency graphs and assess the impact of code and database changes.
Also known as CodeLogicIncEngineering/codelogic-mcp-server
- Stars
- 37
- Tools
- 8
- Downloads, 30 days
- 11
- Latest version
- 1.3.0
- Last commit
- Oct 26, 2026
- License
- MPL-2.0
What is Lineai MCP?
Lineai lets AI coding assistants query software dependency graphs and assess the impact of code and database changes. It exposes 8 tools, such as lineai-method-impact, lineai-database-impact, lineai-graph-capabilities.
Summary generated from the project's README
About Lineai MCP server
Analyzing how code modifications or database changes affect your software architecture is what codelogic-mcp-server enables for developers using AI programming assistants. By connecting to Lineai's software dependency data, the server allows tools like Claude Desktop, Cursor, VS Code with GitHub Copilot, and Windsurf to perform deep impact assessments and navigate complex dependency graphs.
Users interact with the server through eight specialized tools, including lineai-method-impact for analyzing specific class methods and lineai-database-impact for evaluating changes to columns, tables, or views. The server also provides graph-based capabilities such as lineai-graph-search for finding nodes, lineai-graph-path-explain to find connections between entities, and lineai-graph-validate-change-scope to generate risk summaries for proposed updates.
Setup requires the Astral UV tool and connection to a Lineai server host using credentials like LINEAI_USERNAME and LINEAI_PASSWORD. The server functions locally via stdio and can be scoped to specific workspaces or materialized views through environment variables or direct tool arguments.
What you can do with it
- 1Assess method change impactDetermine which parts of a codebase are affected by modifying a specific class method.
- 2Evaluate database schema changesAnalyze how altering a database table or column might impact existing code.
- 3Identify code ownersFind the responsible parties for a specific node or piece of code within the graph.
- 4Validate proposed changesGet a heuristic risk summary for a planned code modification.
Written from the project's README. Every use case is checked against a quote from it.
How to install Lineai MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Lineai MCP in Claude Code
$ claude mcp add --env 'CODELOGIC_PASSWORD=<YOUR_CODELOGIC_PASSWORD>' --env 'CODELOGIC_SERVER_HOST=<CODELOGIC_SERVER_HOST>' --env 'CODELOGIC_USERNAME=<CODELOGIC_USERNAME>' --env 'CODELOGIC_WORKSPACE_NAME=<CODELOGIC_WORKSPACE_NAME>' codelogic-mcp-server -- uvx codelogic-mcp-serverInstall Lineai MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"codelogic-mcp-server": {
"command": "uvx",
"args": [
"codelogic-mcp-server"
],
"env": {
"CODELOGIC_PASSWORD": "<YOUR_CODELOGIC_PASSWORD>",
"CODELOGIC_SERVER_HOST": "<CODELOGIC_SERVER_HOST>",
"CODELOGIC_USERNAME": "<CODELOGIC_USERNAME>",
"CODELOGIC_WORKSPACE_NAME": "<CODELOGIC_WORKSPACE_NAME>"
}
}
}
}Install Lineai MCP in VS Code
.vscode/mcp.json
{
"servers": {
"codelogic-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"codelogic-mcp-server"
],
"env": {
"CODELOGIC_PASSWORD": "<YOUR_CODELOGIC_PASSWORD>",
"CODELOGIC_SERVER_HOST": "<CODELOGIC_SERVER_HOST>",
"CODELOGIC_USERNAME": "<CODELOGIC_USERNAME>",
"CODELOGIC_WORKSPACE_NAME": "<CODELOGIC_WORKSPACE_NAME>"
}
}
}
}Install Lineai MCP in VS Code CLI
$ code --add-mcp '{"name":"codelogic-mcp-server","type":"stdio","command":"uvx","args":["codelogic-mcp-server"],"env":{"CODELOGIC_PASSWORD":"<YOUR_CODELOGIC_PASSWORD>","CODELOGIC_SERVER_HOST":"<CODELOGIC_SERVER_HOST>","CODELOGIC_USERNAME":"<CODELOGIC_USERNAME>","CODELOGIC_WORKSPACE_NAME":"<CODELOGIC_WORKSPACE_NAME>"}}'Install Lineai MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"codelogic-mcp-server": {
"command": "uvx",
"args": [
"codelogic-mcp-server"
],
"env": {
"CODELOGIC_PASSWORD": "<YOUR_CODELOGIC_PASSWORD>",
"CODELOGIC_SERVER_HOST": "<CODELOGIC_SERVER_HOST>",
"CODELOGIC_USERNAME": "<CODELOGIC_USERNAME>",
"CODELOGIC_WORKSPACE_NAME": "<CODELOGIC_WORKSPACE_NAME>"
}
}
}
}Install Lineai MCP in Codex
$ codex mcp add codelogic-mcp-server --env 'CODELOGIC_PASSWORD=<YOUR_CODELOGIC_PASSWORD>' --env 'CODELOGIC_SERVER_HOST=<CODELOGIC_SERVER_HOST>' --env 'CODELOGIC_USERNAME=<CODELOGIC_USERNAME>' --env 'CODELOGIC_WORKSPACE_NAME=<CODELOGIC_WORKSPACE_NAME>' -- uvx codelogic-mcp-serverInstall Lineai MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.codelogic-mcp-server] command = "uvx" args = ["codelogic-mcp-server"] [mcp_servers.codelogic-mcp-server.env] CODELOGIC_PASSWORD = "<YOUR_CODELOGIC_PASSWORD>" CODELOGIC_SERVER_HOST = "<CODELOGIC_SERVER_HOST>" CODELOGIC_USERNAME = "<CODELOGIC_USERNAME>" CODELOGIC_WORKSPACE_NAME = "<CODELOGIC_WORKSPACE_NAME>"
Install Lineai MCP in Gemini CLI
$ gemini mcp add -s user -e 'CODELOGIC_PASSWORD=<YOUR_CODELOGIC_PASSWORD>' -e 'CODELOGIC_SERVER_HOST=<CODELOGIC_SERVER_HOST>' -e 'CODELOGIC_USERNAME=<CODELOGIC_USERNAME>' -e 'CODELOGIC_WORKSPACE_NAME=<CODELOGIC_WORKSPACE_NAME>' codelogic-mcp-server uvx -- codelogic-mcp-serverInstall Lineai MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"codelogic-mcp-server": {
"command": "uvx",
"args": [
"codelogic-mcp-server"
],
"env": {
"CODELOGIC_PASSWORD": "<YOUR_CODELOGIC_PASSWORD>",
"CODELOGIC_SERVER_HOST": "<CODELOGIC_SERVER_HOST>",
"CODELOGIC_USERNAME": "<CODELOGIC_USERNAME>",
"CODELOGIC_WORKSPACE_NAME": "<CODELOGIC_WORKSPACE_NAME>"
}
}
}
}Lineai MCP tools 8
Detected from the READMElineai-method-impactlineai-database-impactlineai-graph-capabilitieslineai-graph-searchlineai-graph-impactlineai-graph-path-explainlineai-graph-validate-change-scopelineai-graph-owners
Configuration
CODELOGIC_PASSWORDRequiredSecretCodeLogic server password
CODELOGIC_SERVER_HOSTRequiredurl to the CodeLogic server e.g. https://myco.app.codelogic.com
CODELOGIC_USERNAMERequiredCodeLogic server username
CODELOGIC_WORKSPACE_NAMERequiredthe workspace name that your code is scanned into
CODELOGIC_DEBUG_MODEWhen enabled, additional debug files such as timing_log.txt and impact_data*.json will be generated. Defaults to false
LINEAI_DEBUG_MODELINEAI_PASSWORDLINEAI_SERVER_HOSTLINEAI_USERNAMELINEAI_WORKSPACE_NAME
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHublineai-mcp-server
An MCP Server to utilize Lineai's rich software dependency data in your AI programming assistant.
Documentation
Code-derived architecture documentation lives in docs/ (added in
LIN-737; updated for the LIN-699 changes — PR #61 / neo4cape #1860):
- docs/architecture.md — full architecture analysis: module map, tool surface and the Lineai
/api/...endpoints each tool calls, auth flow, caching, error-handling taxonomy, configuration, packaging/release, and findings. - docs/architecture-diagrams.md — Mermaid diagram set (ecosystem, module map, call sequence, auth/caching, error taxonomy).
- docs/rendered-diagrams/ — committed SVG renders of every diagram.
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. Pass the fully-qualified class name in "class" (e.g.
com.acme.shell.AnalyzeCommands) when the simple name may exist in several repositories: a fully-qualified class selects exactly that class, while a simple name that matches several classes returns an ambiguity page listing the candidates instead of silently analyzing another repository's class. - The impact is a bounded upstream traversal from the Lineai graph impact endpoint (
depthargument, default 3, max 10). The report's Impact scope section says where the data came from (graph, or the legacy full-chain endpoint when the graph endpoint is not deployed) and whether it is complete (ok) or a lower bound (partial) — a partial result is never "no impact".
- Takes the given "method" that you're working on. Pass the fully-qualified class name in "class" (e.g.
- lineai-database-impact: Analyzes impacts between code and database entities.
- Takes the database entity type (column, table, or view) and its name.
All eight tools also accept optional workspace and materialized_view_id arguments to scope a single call; when neither is given (and LINEAI_WORKSPACE_NAME is unset) the server's default workspace's latest materialized view is used automatically.
Graph API tools
These call POST / GET endpoints under /api/ai-retrieval/graph/ on the same host as LINEAI_SERVER_HOST, 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 (materializedViewIdresolved like every other tool: explicit id →workspaceargument →LINEAI_WORKSPACE_NAME→ server default). - lineai-graph-search: Search nodes by text
query/qand/oridentity_prefix; optionalscan_space(scan space id or display name),prefer_latest_scan,limit. Results are ranked by the server (exact short name → exact fully-qualified name → class-like labels → text score → newest scan) anddata.hits[i]describesdata.nodes[i](score,matchKind,labelTier);data.totalHitCountis the real total, so a full page means "narrow the query", not "absent". - lineai-graph-impact: Bounded dependency / blast-radius traversal from
seed_node_idswithdirection(upstream= what depends on the seeds,downstream,both) anddepth(server default 3, max 10). The response carriesstatus(ok|partial),truncated,nodeCount,staticAnalysisGapandassumptionsAppliedmarkers; the tool prints a note above the JSON whenever the result is partial, degraded, or an older server ignored an option. - lineai-graph-path-explain: Shortest-path style explanation between
from_node_idandto_node_id. - lineai-graph-validate-change-scope: Heuristic checklist / risk summary for a proposed change given seed nodes and
proposed_change_summary. - lineai-graph-owners: Resolve a node by
node_idoridentity_prefixand surface property fields whose names contain"owner".
Tool arguments accept snake_case aliases (for example materialized_view_id, seed_node_ids) 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:
- Clone this project locally.
- Configure your
mcp.jsonto useuvinstead ofuvx. 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"
}
}
}
}
- Restart Cursor.
- Ensure the Cursor Global Rule for Lineai is in place.
- Open the MCP tab in Cursor and refresh the
lineai-mcp-server. - 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:
-
First, ensure you have GitHub Copilot agent mode enabled in VS Code.
-
Create a
.vscode/mcp.jsonfile in your workspace with the following configuration:
{
"servers": {
"lineai-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"lineai-mcp-server@latest"
],
"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"
}
}
}
}
Note: On some systems, you may need to use the full path to the uvx executable instead of just "uvx". For example:
/home/user/.local/bin/uvxon Linux/Mac orC:\Users\username\AppData\Local\astral\uvx.exeon Windows.
-
Alternatively, you can run the
MCP: Add Servercommand from the Command Palette and provide the server information. -
To manage your MCP servers, use the
MCP: List Serverscommand from the Command Palette. -
Once configured, the server's tools will be available to Copilot agent mode. You can toggle specific tools on/off as needed by clicking the Tools button in the Chat view when in agent mode.
-
To use the Lineai tools in agent mode, you can specifically ask about code impacts or database relationships, and the agent will utilize the appropriate tools.
Claude Desktop Configuration
Configure Claude Desktop by editing the configuration file:
- On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json - On Windows:
%APPDATA%/Claude/claude_desktop_config.json - On Linux:
~/.config/Claude/claude_desktop_config.json
Add the following to your configuration file:
"mcpServers": {
"lineai-mcp-server": {
"command": "uvx",
"args": [
"lineai-mcp-server@latest"
],
"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>"
}
}
}
Note: On some systems, you may need to use the full path to the uvx executable instead of just "uvx". For example:
/home/user/.local/bin/uvxon Linux/Mac orC:\Users\username\AppData\Local\astral\uvx.exeon Windows.
After adding the configuration, restart Claude Desktop to apply the changes.
Windsurf IDE Configuration
To run this MCP server with Windsurf IDE:
Configure Windsurf IDE:
To configure Windsurf IDE, you need to create or modify the ~/.codeium/windsurf/mcp_config.json configuration file.
Add the following configuration to your file:
"mcpServers": {
"lineai-mcp-server": {
"command": "uvx",
"args": [
"lineai-mcp-server@latest"
],
"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>"
}
}
}
Note: On some systems, you may need to use the full path to the uvx executable instead of just "uvx". For example:
/home/user/.local/bin/uvxon Linux/Mac orC:\Users\username\AppData\Local\astral\uvx.exeon Windows.
After adding the configuration, restart Windsurf IDE or refresh the tools to apply the changes.
Cursor Configuration
To configure the Lineai MCP server in Cursor:
- Configure the MCP server by creating a
.cursor/mcp.jsonfile:
{
"mcpServers": {
"lineai-mcp-server": {
"command": "uvx",
"args": [
"lineai-mcp-server@latest"
],
"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"
}
}
}
}
Note: On some systems, you may need to use the full path to the uvx executable instead of just "uvx". For example:
/home/user/.local/bin/uvxon Linux/Mac orC:\Users\username\AppData\Local\astral\uvx.exeon Windows.
- Restart Cursor to apply the changes.
The Lineai MCP server tools will now be available in your Cursor workspace.
AI Assistant Instructions/Rules
To help the AI assistant use the Lineai tools effectively, you can add the following instructions/rules to your client's configuration. We recommend customizing these instructions to align with your team's specific coding standards, best practices, and workflow requirements:
When the graph API is available on your Lineai host, extend your rules with the same guidance the server already advertises in its MCP instructions: use lineai-graph-* tools (search, impact, path-explain, validate-change-scope, owners, capabilities) for bounded graph discovery; if graph calls fail with “not available”, fall back to lineai-method-impact / lineai-database-impact.
VS Code (GitHub Copilot) Instructions
Create a .vscode/copilot-instructions.md file with the following content:
# Lineai MCP Server Instructions
When modifying existing code methods:
- Use lineai-method-impact to analyze code changes
- Use lineai-database-impact for database modifications
- When the Lineai graph API is available, use lineai-graph-* tools (search, impact, path-explain, validate-change-scope, owners, capabilities) for bounded graph discovery; otherwise rely on method/database impact tools
- Highlight impact results for the modified methods
When modifying SQL code or database entities:
- Always use lineai-database-impact to analyze potential impacts
- Highlight impact results for the modified database entities
To use the Lineai tools effectively:
- For code impacts: Ask about specific methods or functions
- For database relationships: Ask about tables, views, or columns
- For graph discovery: Prefer lineai-graph-* tools when available
- Review the impact results before making changes
- Consider both direct and indirect impacts
Claude Desktop Instructions
Create a file ~/.claude/instructions.md with the following content:
# Lineai MCP Server Instructions
When modifying existing code methods:
- Use lineai-method-impact to analyze code changes
- Use lineai-database-impact for database modifications
- When the Lineai graph API is available, use lineai-graph-* tools (search, impact, path-explain, validate-change-scope, owners, capabilities) for bounded graph discovery; otherwise rely on method/database impact tools
- Highlight impact results for the modified methods
When modifying SQL code or database entities:
- Always use lineai-database-impact to analyze potential impacts
- Highlight impact results for the modified database entities
To use the Lineai tools effectively:
- For code impacts: Ask about specific methods or functions
- For database relationships: Ask about tables, views, or columns
- For graph discovery: Prefer lineai-graph-* tools when available
- Review the impact results before making changes
- Consider both direct and indirect impacts
Windsurf IDE Rules
Create or modify the ~/.codeium/windsurf/memories/global_rules.md markdown file with the following content:
When modifying existing code methods:
- Use lineai-method-impact to analyze code changes
- Use lineai-database-impact for database modifications
- When the Lineai graph API is available, use lineai-graph-* tools (search, impact, path-explain, validate-change-scope, owners, capabilities) for bounded graph discovery; otherwise rely on method/database impact tools
- Highlight impact results for the modified methods
When modifying SQL code or database entities:
- Always use lineai-database-impact to analyze potential impacts
- Highlight impact results for the modified database entities
To use the Lineai tools effectively:
- For code impacts: Ask about specific methods or functions
- For database relationships: Ask about tables, views, or columns
- For graph discovery: Prefer lineai-graph-* tools when available
- Review the impact results before making changes
- Consider both direct and indirect impacts
Cursor Global Rule
To configure Lineai rules in Cursor:
- Open Cursor Settings
- Navigate to the "Rules" section
- Add the following content to "User Rules":
# Lineai MCP Server Rules
## Codebase
- The Lineai MCP Server is for java, javascript, typescript, and C# dotnet codebases
- don't run the tools on python or other non supported codebases
## AI Assistant Behavior
- When modifying existing code methods:
- Use lineai-method-impact to analyze code changes
- Use lineai-database-impact for database modifications
- When the Lineai graph API is available, use lineai-graph-* tools (search, impact, path-explain, validate-change-scope, owners, capabilities) for bounded graph discovery; otherwise rely on method/database impact tools
- Highlight impact results for the modified methods
- When modifying SQL code or database entities:
- Always use lineai-database-impact to analyze potential impacts
- Highlight impact results for the modified database entities
- To use the Lineai tools effectively:
- For code impacts: Ask about specific methods or functions
- For database relationships: Ask about tables, views, or columns
- Review the impact results before making changes
- Consider both direct and indirect impacts
Environment Variables
The following environment variables can be configured to customize the behavior of the server:
LINEAI_SERVER_HOST: The URL of the Lineai server (required). All API paths (/api/authenticate,/api/ai-retrieval/...,/api/dependency/...,/api/materialized-view...) are appended to it.LINEAI_USERNAME: Your Lineai username (required).LINEAI_PASSWORD: Your Lineai password (required).LINEAI_WORKSPACE_NAME: The default workspace to use. Optional: individual tool calls can override it withworkspace/materialized_view_idarguments, and when nothing is specified at all the server's default workspace's latest materialized view is used.LINEAI_DEBUG_MODE: Set totrueto enable debug mode. When enabled, additional debug files such astiming_log.txtandimpact_data*.jsonwill be generated. Defaults tofalse.
Tuning (optional — read once at server startup)
LINEAI_TOKEN_CACHE_TTL: Authentication-token cache lifetime in seconds. Defaults to3600.LINEAI_METHOD_CACHE_TTL: Method shortname-search result cache lifetime in seconds. Defaults to300.LINEAI_IMPACT_CACHE_TTL: Impact-analysis result cache lifetime in seconds. Defaults to300.LINEAI_MV_CACHE_TTL: Materialized-view resolution cache lifetime in seconds (workspace name / server default → view id). Defaults to300.LINEAI_REQUEST_TIMEOUT: Overall HTTP request timeout in seconds for all Lineai API calls. Defaults to120.0. Graph impact calls are bounded server-side (depth / node / relationship caps, 60 s query timeout), so a timeout here usually means the depth is too large — retry withdepth1–2.LINEAI_CONNECT_TIMEOUT: HTTP connect timeout in seconds. Defaults to30.0.LINEAI_METHOD_IMPACT_BACKEND:graph(default) fetches thelineai-method-impactsubgraph from the bounded graph impact endpoint and falls back to the legacy/api/dependency/impact/fulllist only when the graph route is missing (a 404 without neo4cape's entity message); a 404 that names the node ("Unable to locate node …") is reported as a search/view disagreement instead, because the legacy traversal from an unknown id returns an empty result that would read as "isolated";legacyforces the legacy endpoint (unbounded full incoming chain). Read per call.
Tests only
LINEAI_TEST_MODE: When set (any value), the server skips loading a.envfile so tests fully control the environment.LINEAI_GRAPH_E2E_REQUIRED: Set to1when running graph MCP integration tests if you want missing graph APIs (HTTP 404 / “Graph API not available”) to fail the suite instead of skipping those tests.
Example Configuration
"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"
}
Pinning the version
instead of using the latest version of the server, you can pin to a specific version by changing the args field to match the version in pypi e.g.
"args": [
"lineai-mcp-server@0.2.2"
],
Version Compatibility
This MCP server has the following version compatibility requirements:
- Version 0.3.1 and below: Compatible with all Lineai API versions
- Version 0.4.0 and above: Requires Lineai API version 25.10.0 or greater
If you're upgrading, make sure your Lineai server meets the minimum API version requirement.
Graph tools: Require your Lineai deployment to serve the graph endpoints under /api/ai-retrieval/graph/. Older or partial deployments may return 404; the MCP tools surface that as a clear error instead of opaque failures.
Ranked search / bounded impact (LIN-870): ranking, hits, the real totalHitCount, scan_space / prefer_latest_scan, and the depth / direction / status: partial impact contract need a Lineai server that includes neo4cape LIN-870. Against an older server the tools still work: search comes back in the server's unranked order, impact runs the full subgraph, and the ignored options are echoed as *_not_implemented / *_reserved_* markers that the tool renders as "x was ignored (older server)". lineai-method-impact falls back to the legacy impact endpoint automatically when the graph endpoint is missing.
Debug Logging
When LINEAI_DEBUG_MODE=true, debug files are written to the system temporary directory:
- Windows:
%TEMP%\lineai-mcp-server(typicallyC:\Users\{username}\AppData\Local\Temp\lineai-mcp-server) - macOS:
/tmp/lineai-mcp-server(or$TMPDIR/lineai-mcp-serverif set) - Linux:
/tmp/lineai-mcp-server(or$TMPDIR/lineai-mcp-serverif set)
Debug files include:
timing_log.txt- Performance timing informationimpact_data_*.json- Raw impact analysis data for troubleshooting
Finding your log directory:
import tempfile
import os
print("Log directory:", os.path.join(tempfile.gettempdir(), "lineai-mcp-server"))
Testing
Running Unit Tests
The project uses unittest for testing. You can run unit tests without any external dependencies:
python -m unittest discover -s test -p "unit_*.py"
Unit tests use mock data and don't require a connection to a Lineai server. test/unit_test_handlers.py includes the TestMethodNodeSelection table (the LIN-870 AnalyzeCommands-in-three-repositories case: fully-qualified class → the right repository, simple name → ambiguity page, foreign fully-qualified name → not-found page, unresolved references never chosen) and the graph-backend / legacy-fallback / partial-result handler cases; test/unit_test_graph_tools.py covers the partiality note and old-server markers.
Integration Tests (Optional)
If you want to run integration tests that connect to a real Lineai server:
- Copy
test/.env.test.exampletotest/.env.testand populate with your Lineai server details - Run the integration tests:
python -m unittest discover -s test -p "integration_*.py"
Note: Integration tests require access to a Lineai server instance.
Graph MCP end-to-end tests
test/integration_test_graph.py drives the real MCP handler path (handle_call_tool) for lineai-graph-capabilities and a chained flow (search → impact → path → validate → owners) against LINEAI_SERVER_HOST. Configure credentials the same way as other integration tests (test/.env.test from test/.env.test.example).
- If the host does not expose graph routes, tests skip by default.
- Set
LINEAI_GRAPH_E2E_REQUIRED=1to turn missing graph APIs into hard failures (useful in CI when graph must be present).
From the repo root:
./scripts/run_graph_e2e.sh
Equivalent:
uv run python -m unittest test.integration_test_graph -v
Validation for Official MCP Registry
mcp-name: io.github.lineai-intelligence/lineai-mcp-server
Lineai MCP questions
How do I add Lineai MCP to Claude Code?
Run claude mcp add --env 'CODELOGIC_PASSWORD=<YOUR_CODELOGIC_PASSWORD>' --env 'CODELOGIC_SERVER_HOST=<CODELOGIC_SERVER_HOST>' --env 'CODELOGIC_USERNAME=<CODELOGIC_USERNAME>' --env 'CODELOGIC_WORKSPACE_NAME=<CODELOGIC_WORKSPACE_NAME>' codelogic-mcp-server -- uvx codelogic-mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Lineai MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Lineai MCP provide?
It exposes 8 tools, including lineai-method-impact, lineai-database-impact, lineai-graph-capabilities, lineai-graph-search, lineai-graph-impact.
What does the Lineai MCP server let my AI assistant do?
It lets the assistant run impact assessments on methods and database entities and explore dependency graphs via graph search, impact, path explanation and change-scope validation tools.
How do I authenticate the Lineai MCP server?
You provide environment variables with your Lineai server host, username and password in your MCP client configuration.
Which IDEs and clients can I configure Lineai MCP with?
The README covers VS Code with GitHub Copilot, Claude Desktop, Windsurf IDE and Cursor.
What does the method impact tool do?
It pulls an impact assessment from Lineai's APIs for a given method, doing a bounded upstream traversal with a default depth of 3.
What happens if the graph API is not deployed?
The server returns a clear "graph not available" style message, and you can fall back to the method and database impact tools.