mdapi-sync-calls-require-asyncio-to-thread-wrapping
simple-salesforce metadata API calls (mdapi.deploy, mdapi.retrieve, etc.) are synchronous blocking operations. In an async FastMCP server context, they must be wrapped with asyncio.to_thread() to avoid blocking the event loop. Missing this wrapper can cause server hangs under concurrent load.
Related
- salesforce
- sf-deploy-metadata-mcp-tool-bug-missing-sandbox-param
- markit-sdk-hono-integration-patterns
- docker
- salesforce-mcp-tools-may-not-appear-despite-permanent-regist
- mdapi-deploy-blocking-requires-asyncio-to-thread
- salesforce-mcp-inline-tool-overrides-module-tool-silently
- salesforce-mcp-mdapi-calls-must-be-async-wrapped
- simple-salesforce-all-mdapi-calls-are-synchronous-must-wrap
- simple-salesforce-mdapi-sync-calls-need-asyncio-to-thread
- mdapi-sync-calls-in-async-functions-require-asyncio-to-threa
- simple-salesforce-mdapi-sync-must-wrap-asyncio-to-thread
- salesforce-mcp-23-mdapi-calls-missing-asyncio-to-thread