Glama

Connect Glama to Suped's MCP server to work with your organizations, domains, email authentication issues, and DMARC reports. The connection uses your Suped account and its existing organization permissions.

Connect Suped

1. Open the Suped DMARC connector on Glama and choose Add Connector. Sign in to Glama if prompted.
2. Follow the connector's OAuth connection flow. Sign in to Suped and approve access for the client shown on the authorization screen.
3. Return to Glama and use the connected Suped tools. Start by listing your organizations so subsequent requests target the correct organization or MSP client.

If you are entering the server manually, use this URL with Streamable HTTP and OAuth:

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

Suped supports automatic OAuth client registration. You do not need a Suped REST API key or a client secret. See the MCP server guide for connection details.

Try it

• “List the Suped organizations I can access.”
• “Show the open authentication issues for Example Company.”
• “Summarize Example Company's DMARC results for the last week.”
• “Add example.com to Example Company in Suped.”

Suped can also return original DMARC report XML and create client organizations under an MSP you administer. Report data is available after DMARC reporting is configured and reports have arrived. Adding a domain does not change DNS, and the tools cannot resolve, dismiss, or edit issues.

Access and troubleshooting

OAuth uses the suped:write scope for both reading and creating data. It does not grant access to additional organizations. Reading domains, reports, and issues, 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 an organization is missing, confirm that the connected Suped account can access it. If Glama asks you to authenticate again, reconnect through OAuth. For an empty report result, check the selected organization and date range in Suped.