From ba938c9b9b94d6e3f37e3534144ae5180ad7e93c Mon Sep 17 00:00:00 2001
From: Lars Varming <lars.varming@gmail.com>
Date: Sun, 9 Nov 2025 22:13:05 +0100
Subject: [PATCH] Add SEMAPHORE_LIMIT logging to startup configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Log the SEMAPHORE_LIMIT value at startup to help users verify their
concurrency control settings are being applied correctly. This is
especially useful when troubleshooting rate limit issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
---
 mcp_server/src/graphiti_mcp_server.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/mcp_server/src/graphiti_mcp_server.py b/mcp_server/src/graphiti_mcp_server.py
index 636a6da0..c611a2ae 100644
--- a/mcp_server/src/graphiti_mcp_server.py
+++ b/mcp_server/src/graphiti_mcp_server.py
@@ -1541,6 +1541,7 @@ async def initialize_server() -> ServerConfig:
     logger.info(f'  - Database: {config.database.provider}')
     logger.info(f'  - Group ID: {config.graphiti.group_id}')
     logger.info(f'  - Transport: {config.server.transport}')
+    logger.info(f'  - Semaphore Limit: {SEMAPHORE_LIMIT}')
 
     # Log graphiti-core version
     try: