mcp-server-patterns

To build an MCP server for Salesforce, use Node and TypeScript patterns to register tools, resources, and prompts. Apply schema validation with Zod and choose a transport like stdio or streamable HTTP to expose operations such as SOQL queries.

Choose stdio for local MCP server transport during development, and use streamable HTTP for production deployments. Legacy HTTP/SSE is also supported, but keeping server logic transport-agnostic allows you to switch between these options as needed.

Zod schema validation secures MCP tool registration by enforcing strict input types and sanitization. This ensures that parameters passed to Salesforce CLI operations, like SOQL queries, are validated before execution to prevent unsafe inputs.

Yes, you can scaffold a custom MCP server that registers a Zod-validated search tool. This tool performs SOQL via the Salesforce CLI and is fully compatible with MCP clients like Claude or Cursor for direct Salesforce record searches.

Best practices for Salesforce MCP servers include schema-first validation with Zod, explicit timeouts, and idempotency practices. Secure execution of Salesforce CLI calls and proper input sanitization are also critical for safe server operation.

Yes, these MCP server patterns support compatibility with both @salesforce/mcp and Context7 registration APIs. This ensures that your registered tools, resources, and prompts are discoverable across evolving SDK signatures.