salesforce-mcp-registered-but-absent-from-deferred-tools
Even when Salesforce MCP servers are permanently registered in ~/.claude.json, they may fail to appear in the deferred tools list at session startup due to a connection failure at launch time. This is distinct from the cert-error pattern — the server itself is healthy and reachable. Workaround: initialize a session via curl POST to the Streamable HTTP endpoint, capture the Mcp-Session-Id header, and run tools/call requests directly.
Related
- salesforce-mcp-tools-absent-from-deferred-list-despite-regis
- mid-session-claude-mcp-add-s-project-doesn-t-load-tools
- 2026-04-04-oracle-001-self-architecture-analysis
- aj-ea-core-mcp-servers-permanently-registered
- salesforce
- case-key-handover-date-field-location-and-semantics
- salesforce-mcp-tools-may-not-appear-despite-permanent-regist
- mcp-server-registrations-bloat-context-of-unused-workspaces
- simple-salesforce-deploy-expects-filepath-not-base64
- inline-imports-inside-async-functions-violate-module-level-c
- salesforce-mcp-session-connection-failure-use-curl
- salesforce-mcp-session-drop-requires-http-fallback
- salesforce-mcp-tunnel-drop-vs-cert-error-distinction
- salesforce-mcp-desktop-tunnel-is-fragile-for-long-sessions
- salesforce-mcp-endpoint-no-auth-required
- salesforce-mcp-tunnel-drops-while-container-healthy
- salesforce-mcp-tunnel-drop-container-healthy-pattern
- xint-mcp-sse-transport-fails-use-http-streamable
- xint-mcp-sse-transport-fails-use-http-at-mcp-endpoint
- redash-query-runner-extensibility-is-primary-integration-poi