mirror of
https://github.com/open-webui/mcpo.git
synced 2026-07-22 11:45:46 -04:00
issue: Reference MCP Server (Sequential Thinking) not compatible with mcpo #38
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @enving on GitHub (Apr 17, 2025).
Check Existing Issues
mcpo Version
v0.0.12
Open WebUI Version (if applicable)
v0.6.5
Operating System
Ubuntu 24.04
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
The integration of the Sequential Thinking MCP server with OpenWebUI should work correctly. When a user makes a request that requires sequential thinking, OpenWebUI should be able to call the
/sequentialthinking/sequentialthinkingendpoint with properly typed JSON parameters, and the tool should perform a step-by-step analysis.Actual Behavior
The integration of the Sequential Thinking MCP server with OpenWebUI should work correctly. When a user makes a request that requires sequential thinking, OpenWebUI should be able to call the
http://mcpo:8000/sequentialthinkingendpoint with properly typed JSON parameters, and the tool should perform a step-by-step analysis.We get a error in the container logs: ""Input should be a valid integer, unable to parse string as an integer"
The problem appears to be a data type incompatibility issue between OpenWebUI and the Sequential Thinking server. OpenWebUI sends parameters as strings (also for null values and booleans), while the API expects concrete types (integer, boolean, null).
Steps to Reproduce
Create a Docker Compose setup with OpenWebUI and MCPO Server
Configure Sequential Thinking in the config.json:
"sequentialthinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
Configure in Openwebui:
http://mcpo:8000/sequentialthinkingActivate native function calling to see the status in the chat fenster or leave it off and see in container logs
In a chat, ask a question that requires sequential thinking, e.g., "Analyze step by step the business model of 1komma5.com"
The MCPO logs show a 422 error
The manual curl command works fine:
curl -X POST "http://localhost:8000/sequentialthinking/sequentialthinking"
-H "Content-Type: application/json"
-H "Authorization: Bearer ..."
-d '{
"thought": "I am analyzing the business model of 1komma5.com",
"nextThoughtNeeded": true,
"thoughtNumber": 1,
"totalThoughts": 5
}'
But the request generated by OpenWebUI fails.
Logs & Screenshots
Faulty request from OpenWebUI to the Sequential Thinking server:
Error Message in MCPO container logs:
docker logs mcpo
{
"error": "HTTP error 422: {"detail":[{"type":"int_parsing","loc":["body","revisesThought"],"msg":"Input should be a valid integer, unable to parse string as an integer","input":"null"},{"type":"int_parsing","loc":["body","branchFromThought"],"msg":"Input should be a valid integer, unable to parse string as an integer","input":"null"}]}"
}
Error message in UI:
{
"thought": "Let's break down the business model of 1komma5.com into its key components and analyze each step in detail.",
"next_thought_needed": "True",
"thought_number": "1",
"total_thoughts": "5",
"is_revision": "False",
"revises_thought": "null",
"branch_from_thought": "null",
"branch_id": "null",
"needs_more_thoughts": "False"
}
{
"error": "HTTP error 422: {"detail":[{"type":"missing","loc":["body","nextThoughtNeeded"],"msg":"Field required","input":{"thought":"Let's break down the business model of 1komma5.com into its key components and analyze each step in detail."}},{"type":"missing","loc":["body","thoughtNumber"],"msg":"Field required","input":{"thought":"Let's break down the business model of 1komma5.com into its key components and analyze each step in detail."}},{"type":"missing","loc":["body","totalThoughts"],"msg":"Field required","input":{"thought":"Let's break down the business model of 1komma5.com into its key components and analyze each step in detail."}}]}"
}
Additional Information
No response