We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/1nbuc/mcp-integration-suite'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
authentication-options-inbound-5495ee0.md•1.01 kB
<!-- loio5495ee0775004999a73ce72a074d6fc7 -->
# Authentication Options \(Inbound\)
For inbound communication, different ways are supported how the sender can authenticate itself against Cloud Integration.
We use **inbound** to refer to the communication direction when a sender system sends a message to the integration platform.
- **Basic authentication**
The calling entity is authenticated based on credentials \(user name and password\).
- **Client-certificate authentication**
- **OAuth 2.0**
OAuth allows you to set up authentication scenarios without the need to share credentials.
See:
- [Protecting Applications with OAuth 2.0](https://help.hana.ondemand.com/help/frameset.htm?b7b589334d444293a2a91e0ef4234136.html)
- [OAuth 2.0 Specification](https://oauth.net/2/)
**Related Information**
[Basic Authentication](basic-authentication-2c4c2d9.md "Basic authentication allows a client to authenticate itself against the server based on user credentials.")