Skip to content

amazon-neptune-mcp-server: StdErr logging forced at INFO level #1581

@brianok-aws

Description

@brianok-aws

Describe the bug

As you can observe at

, Neptune MCP Server adds a logging handler to output STDERR at INFO level. As a result, the logs are filled with messages like

[10/24/25 09:39:46] INFO     Processing request of type CallToolRequest                                    server.py:674

originating from https://github.com/modelcontextprotocol/python-sdk/blob/v1.18.0/src/mcp/server/lowlevel/server.py#L672

Expected Behavior

The Server should respect the FASTMCP_LOG_LEVEL environment variable when determining the logging level.

Current Behavior

INFO level logging is forced.

Reproduction Steps

Set the FASTMCP_LOG_LEVEL to "WARN" and make.a tool call from the Neptune MCP Server. You will still see INFO level calls.

Possible Solution

Implement an approach similar to documentdb-mcp-server

(suggested by @bechbd)

Additional Information/Context

No response

OS

Ubuntu

Server

amazon-neptune-mcp-server

Server Version

latest

Region experiencing the issue

us-east-1

Other information

No response

Service quota

  • I have reviewed the service quotas for this construct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-triageThis needs to be handled, it is the first automatically assigned label to issues.

    Type

    No type

    Projects

    Status

    To triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions