Testing with Postman

Once you've configured Postman with OAuth 2.0 authentication for Salesforce, you can test the MCP server by calling its tools. This page walks through basic testing scenarios to verify your connection is working correctly.

Testing Tools Without Parameters

Some MCP tools don't require any input parameters, making them ideal for initial testing. Two simple examples are describeGlobal and getUserInfo.

To test a tool without parameters:

• In the Message tab, you'll see a list of available tools on the left side
• In the right pane, you'll see a JSON structure with "method": "tools/call" and a "params" section
• Click on a tool name (such as describeGlobal or getUserInfo) in the left pane. Postman automatically populates the JSON in the right pane:

  {
    "method": "tools/call",
    "params": {
      "name": "describeGlobal",
      "arguments": {}
    }
  }

• Click Run in the upper right corner
• View the results in the Response pane at the bottom of the window

For describeGlobal, you'll see a list of all Salesforce objects available in your org. For getUserInfo, you'll see information about the current authenticated user.

Testing Tools With Parameters

Many MCP tools require input parameters. The soqlQuery tool is a good example that lets you execute SOQL queries against your Salesforce org.

To test the soqlQuery tool:

• Click on soqlQuery in the tools list on the left side
• Postman populates the JSON structure in the right pane:

  {
    "method": "tools/call",
    "params": {
      "name": "soqlQuery",
      "arguments": {}
    }
  }

• Add your SOQL query to the arguments object. For example, to query Account records:

  {
    "method": "tools/call",
    "params": {
      "name": "soqlQuery",
      "arguments": {
        "query": "SELECT Id, Name, Type, Industry, Phone, Website, BillingStreet, BillingCity, BillingState, NumberOfEmployees, AnnualRevenue FROM Account WHERE Name = 'Abbott Insurance'"
      }
    }
  }

• Click Run in the upper right corner
• View the query results in the Response pane at the bottom

The response shows the matching Account records with all requested fields.

What to Try Next

Once you've successfully tested these basic tools, you can explore other available tools:

• describeSObject - Get detailed metadata about a specific Salesforce object
• getRelatedRecords - Retrieve related records for a given record
• listRecentSobjectRecords - Get recently viewed records of a specific object type
• find - Search across multiple objects using SOSL

Each tool will have different required and optional parameters. Click on the tool name in Postman to see the parameter structure, then add your specific values in the arguments object before clicking Run.

Important Note About MCP and LLMs

The MCP server itself is completely deterministic and does not involve an LLM for tool calls. When you call a tool directly in Postman, you're making direct API calls to Salesforce and receiving structured responses—no language model is processing your requests or responses.

Postman offers AI-powered developer tools that allow you to connect an LLM to the MCP server responses if you want to test agentic workflows. These AI features are separate capabilities within Postman and are not part of the MCP server itself.