salesforce-mcp-tools-may-not-appear-despite-permanent-registration
Even with Salesforce MCP permanently registered in ~/.claude.json under a workspace, the tools may not appear in the deferred tools list at session startup due to a connection failure at initialization. The server itself can still be reached via direct HTTP curl to the Streamable HTTP endpoint. Workaround: use curl-based session + tool calls as documented in MEMORY.md Salesforce MCP cert bypass pattern.
Related
- salesforce-mcp-tools-absent-from-deferred-list-despite-regis
- salesforce-mcp-registered-but-absent-from-deferred-tools
- 2026-04-04-oracle-001-self-architecture-analysis
- aj-ea-core-mcp-servers-permanently-registered
- salesforce
- mdapi-sync-calls-require-asyncio-to-thread-wrapping
- inline-imports-inside-async-functions-violate-module-level-c
- salesforce-analytics-report-types-api-returns-nested-categor
- salesforce-mcp-session-connection-failure-use-curl
- salesforce-mcp-session-drop-requires-http-fallback
- salesforce-mcp-tunnel-drop-vs-cert-error-distinction
- mcp-server-registration-requires-session-restart-to-activate
- mcp-server-tool-cache-stale-after-mid-session-rebuild