Postman

Use Postman to connect to Suped's MCP server, inspect tool arguments, and run individual requests. Start with the Suped DMARC MCP Server collection or create an MCP request directly in your Postman workspace.

Connect to Suped

1. In Postman, create an MCP request and select HTTP as the communication method. Enter the server URL below.
2. Open Authorization and select OAuth 2.0, then connect. Postman's OAuth flow can discover Suped's settings and register a client automatically.
3. If the OAuth Debugger opens, use Continue to advance through discovery, client registration, and authorization. Sign in to Suped when the browser opens, review the requesting client, and approve access. Return to Postman to finish the token exchange.
4. Load the server's capabilities and open Tools to inspect the available tools.

https://www.suped.com/api/mcp

The endpoint uses Streamable HTTP. Suped REST API keys do not authenticate MCP requests, and Suped's OAuth registration does not require a client secret. For manual OAuth configuration, use the endpoints and parameters in the MCP authentication guide.

Run your first requests

1. Select list_organizations and run it without arguments. The response contains the organization IDs your Suped account can access.
2. Select get_domains and set organizationId to an ID from that response. Run the request to list that organization's domains, including archived domains.
3. Use the same organization ID with list_issues to inspect authentication issues, or with get_dmarc_records and a start and end date to retrieve DMARC data. Use a returned report ID with download_dmarc_report to retrieve its original XML.

The server also supports adding domains and creating MSP client organizations. Those calls create real Suped data. Adding a domain does not change DNS; issue tools only read existing issues. See the tool reference for parameters and responses.

Permissions and connection problems

Requests use your connected Suped user's current permissions. Reading domains, issues, and reports, or adding domains, requires a user or administrator role. Billing-only access is not sufficient. Creating an MSP client requires administrator access to its parent MSP.

If authentication fails, use Postman's OAuth Debugger to identify the failed step. If a request has no report data, check that the organization has received DMARC reports for the requested date range. For Postman's request controls, see its MCP request documentation.