Connect your AI agent

eWasl exposes an MCP server so AI assistants can publish, schedule, and analyze on your behalf. There are two ways to connect.

Option 1 — OAuth (recommended for hosted clients)

Hosted clients like Claude and ChatGPT connect with OAuth 2.0. You approve the exact scopes on an eWasl consent screen — no key copying, and you can revoke access at any time.

• MCP endpoint: https://app.ewasl.com/api/mcp
• Discovery: the server returns the OAuth metadata via /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, so compatible clients discover the flow automatically (RFC 9728 / RFC 8414).
• Flow: Authorization Code + PKCE (S256). Public clients are PKCE-only; :write scopes always require explicit consent.

Add eWasl as a custom connector in your client, point it at the MCP endpoint, and approve the scopes when the consent screen appears.

Option 2 — API key (CLI, Cursor, custom integrations)

For local tools and your own integrations, paste an API key:

1. Create a key at Settings → API keys with only the scopes you need.
2. Configure your client with the bearer token ewasl_....

// Example: an MCP client config (HTTP transport)
{
  "mcpServers": {
    "ewasl": {
      "url": "https://app.ewasl.com/api/mcp",
      "headers": { "Authorization": "Bearer ewasl_xxxxxxxx" }
    }
  }
}

Per-client setup (Claude Desktop, Cursor, ChatGPT, Windsurf) is covered under MCP → clients.

Scopes

Grant the minimum needed. Common scopes: posts:read, posts:create, ads:read, ads:write, content:create, media:read, copilot. Read-only tools are marked readOnlyHint; writes are marked destructiveHint so the client can confirm before acting.

Revoking access

• API key: delete it under Settings → API keys (effective immediately).
• OAuth client: revoke via the client, or call the revocation endpoint listed in the OAuth authorization-server metadata. Refresh-token reuse is detected and revokes the whole token family.

See the Privacy Policy for what each connector can access.