Xagent Docs
Get started

MCP Providers Configuration

Some built-in MCP tools require OAuth authentication — Google, LinkedIn, and Microsoft services. For these you configure a Client ID and Client Secret per provider.

General Setup

For every provider you register an OAuth application and set an authorized redirect URI. The Xagent format is:

https://<YOUR_XAGENT_DOMAIN>/api/auth/<provider>/callback

Replace <YOUR_XAGENT_DOMAIN> with your deployment domain and <provider> with google, linkedin, or microsoft. Locally it may be http://localhost:8000/api/auth/<provider>/callback.

Google (Drive, Gmail, …)

  1. In the Google Cloud Console, create a project and enable the APIs you need (Google Drive API, Gmail API).
  2. Configure the OAuth consent screen and add the required scopes (e.g. https://www.googleapis.com/auth/drive).
  3. Create an OAuth client ID of type Web application, and add the Xagent callback URL as an authorized redirect URI.
  4. Copy the generated Client ID and Client Secret into your Xagent configuration.

LinkedIn & Microsoft

LinkedIn and Microsoft follow the same pattern — register an OAuth app on the provider, set the matching /api/auth/<provider>/callback redirect URI, and copy the Client ID/Secret into Xagent.

LinkedIn scope restriction

LinkedIn strictly enforces API scopes: the r_member_social scope (needed to read posts) requires the Community Management API product, which is mutually exclusive with the standard Sign-In products. If your integration must read posts, plan the LinkedIn app's product selection accordingly.

Keep secrets safe

Client secrets grant access to the connected accounts. Store them through your deployment's secret management, not in source control.

Next Steps