Stirling MCP configuration

[PersianGru]

Hello,

Please someone help me with setting up MCP server for Stirling-PDF V2
I see the option is available

Every time I am trying to test the connection, I am seeing this in the docker log
ERROR s.s.p.c.CustomAuditEventRepository - Failed to persist audit event (fail-open); principal=<JWT_TOKEN_REDACTED>
org.springframework.dao.DataIntegrityViolationException: could not execute statement [Value too long for column "PRINCIPAL CHARACTER VARYING(255)": "'<JWT_TOKEN_REDACTED>' (~1455 chars)"; SQL statement: insert into audit_events ...]
Caused by: org.h2.jdbc.JdbcSQLDataException: Value too long for column "PRINCIPAL CHARACTER VARYING(255)"

Using Microsoft for auth. and connection is like this
Litellm --> Microsoft EntraID app ---> stirling-pdf

And also auth mode is OAuth 2.1 (external IdP) and I am not able to change it to anything else

Docker compose is:

services:
stirling-pdf:
build:
context: ../..
dockerfile: docker/embedded/Dockerfile.fat
container_name: stirling-pdf-fat
restart: unless-stopped
deploy:
resources:
limits:
memory: 6G
healthcheck:
test: ["CMD-SHELL", "curl -f http://localhost:8080$${SYSTEM_ROOTURIPATH:-''}/api/v1/info/status | grep -q 'UP'"]
interval: 5s
timeout: 10s
retries: 16
ports:
- "8585:8080"
volumes:
- ../../stirling/latest/data:/usr/share/tessdata:rw
- ../../stirling/latest/config:/configs:rw
- ../../stirling/latest/logs:/logs:rw
environment:
DISABLE_ADDITIONAL_FEATURES: "false"
SECURITY_ENABLELOGIN: "true"
FAT_DOCKER: "true"
SYSTEM_DEFAULTLOCALE: en-US
UI_APPNAME: Stirling-PDF
UI_HOMEDESCRIPTION: Full-featured Stirling-PDF with all capabilities
UI_APPNAMENAVBAR: Stirling-PDF Fat
SYSTEM_MAXFILESIZE: "200"
METRICS_ENABLED: "true"
SYSTEM_GOOGLEVISIBILITY: "true"
SHOW_SURVEY: "true"
networks:
- stirling-network

networks:
stirling-network:
driver: bridge

volumes:
stirling-data:
stirling-config:
stirling-logs:

[Frooodle]

MCP is currently in our alpha image not our latest tag, we have some fixes and documentation being rolled out for MCP in 1-2 days

[Frooodle]

We should have a fix merged for your specific issue tomorrow

[PersianGru]

Any update on this?

[Frooodle]

that Value too long for column "PRINCIPAL" error is just noise we have a update in latest alpha that removes that error
Auth type button not working and letting you switch has also been fixed and should appear in alpha tag in about 1 hour.

As for the error itself , The real issue is that your Microsoft Entra ID login token is being rejected, and it is almost always because of an audience mismatch in config

Once youre on latest alpha tag you should get some new settings too in that menu

Microsoft doesn't put your /mcp URL in the token, it puts your app's own ID there, so Stirling rejects it as the wrong audience. Your Issuer URL and Resource ID are otherwise fine.

to fix, on the updated image you will see a field called "Additional accepted audiences" just under Resource ID.
Set it to your Entra app's Application ID URI (or client ID(i)n the Azure portal under your app registration.) If you're not sure which form your tokens use, paste a token into https://jwt.ms/ and copy the aud value.

also if you ever turn on "Require an existing Stirling account", change Username claim from sub to preferred_username otherwise it wont match stirling

[PersianGru]

Thank you for the info. I am cloning the GitHub and running this docker/compose/docker-compose.fat.yml
how to run this using alpha tag?

[PersianGru]

Hi @Frooodle
I did run the alpha and noticed there is a new way of connecting MCP using API which makes everyone job easier :)
However in our setup when sending a request to the MCP server, it is not doing anything. Not sure how to confirm what exactly is the issue
This is our setup:
Open Webui ---{MCP connection}--> LiteLLM ----->Stirling MCP server
One LiteLLLM I can see MCP connection received from Open WebUI but no respond from Stirling MCP server
I am testing with LocalLLM Qwen3.5: 0.8B