Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for codelogic-mcp-server

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to codelogic-mcp-server.

Most discussed

[Bug]: No server info found error when invoking the MCP server on MacOS

Bug Description

When using Cursor on MacOS the following errors are thrown, and the MCP server fails to connect to the CodeLogic instance:

2025-04-16 15:47:22.789 [error] -mcp: Error in MCP: Client closed
2025-04-16 15:47:22.790 [info] -mcp: Handling ListOfferings action
2025-04-16 15:47:22.798 [error] -mcp: No server info found

Steps To Reproduce

  1. Installed Astral UV.
  2. Configured the MCP server in Cursor using the [recommended configuration](https://github.com/CodeLogicIn

Read the thread · 2025-05-09 · open · outside contributor · 1 comment

[Feature]: add information about code owners and reviewers to the MCP content

Is your feature request related to a problem?

CodeLogic has a mechanism for marking java and dotnet code with users who take ownership of the code and users who should review the code changes. See the CodeLogic.Attributes Nuget Gallery for the dotnet attributes.

We should detect these in the impact analysis data and outline them for the MCP client to use.

Describe the solution you'd like

Add a section to the markdown that's retu

Read the thread · 2025-04-10 · closed · 1 comment

[Bug]: materialized-view-definition endpoint throws a 500 when referencing a non-default workspace

Bug Description

When using: CODELOGIC_MV_NAME=TB-3.6.4

the API call fails

Steps To Reproduce

Create the TB-3.6.4 workspace Ask your coding tool to analyze impact for a method Fail!

Expected Behavior

successful impact analysis

Screenshots

No response

Operating System

Windows

Python Version

3.9

Package Version

0.3.1

Client Implementation

Windsurf

Model(s) Used

windsurf

Additional Context

No response

Read the thread · 2025-04-08 · closed · 1 comment

[Feature]: Database Impact Analysis

Is your feature request related to a problem?

The CodeLogic knowledge graph contains information about how changes in code will effect database entities and vice versa. Use the this context when code changes are proposed to methods and/or classes that reference database entities.

Describe the solution you'd like

Create an MCP tool that determines the affected column/table/view and then searches for those via the CodeLogic API's

  • /ai-retrieval/search/column
  • /ai-retrieval/search/tab

Read the thread · 2025-04-02 · closed · 1 comment

[Feature]: Multiple CodeLogic Workspaces

Is your feature request related to a problem?

Today the MCP server requires CODELOGIC_WORKSPACE_NAME. This is fine for single-workspace setups but is cumbersome for general IDE development where a user may switch between multiple CodeLogic workspaces. Manually exporting different env vars or restarting the MCP server to change workspaces slows the workflow and increases configuration friction.

Describe the solution you'd like

  • Query the neo4cape server for the list of available works

Read the thread · 2025-10-16 · open · 0 comments

[Feature]: Update Deprecated items

Is your feature request related to a problem?

The CodeLogic report feature will show deprecated items annotated by java.lang.Deprecated and the resulting target direct link will show a knowledge graph with every deprecated item. We can use this data to update references to deprecated items.

Describe the solution you'd like

Create an MCP tool that determines the deprecated items affected and searches for them using the CodeLogic API's, then use them get the impact analysis via the API

Read the thread · 2025-04-24 · open · outside contributor · 0 comments

[Feature]: Tool Annotations

Is your feature request related to a problem?

I just noticed that there are now some useful tool annotations in the docs, we should probably implement some of them.

Describe the solution you'd like

At the very least

    annotations={
        "readOnlyHint": True
    }

but "title" would be good too

Describe alternatives you've considered

No response

Additional context

No response

Read the thread · 2025-04-23 · open · 0 comments

Most recent

The remaining reports are on the project's issue tracker.