Asgardeo authenticates users accessing the MCP server and allows you to control tool access based on application-level and organization-level
Cloudflare MCP Asgardeo MCP server exists for a simple reason — assistants are far more useful when they can act on Cloudflare MCP Asgardeo directly instead of describing what you should do. Asgardeo authenticates users accessing the MCP server and allows you to control tool access based on application-level and organization-level permissions defined for each user.
Once Cloudflare MCP Asgardeo is connected, these are the calls the assistant has available:
client — id** from the Protocol tabThe server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 4 environment variables: ASGARDEO_CLIENT_ID, ASGARDEO_CLIENT_SECRET, ASGARDEO_BASE_URL, COOKIE_ENCRYPTION_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cloudflare MCP Asgardeo's toolset — client — is a fair guide to whether it matches your workflow. It is maintained by sagara-gunathunga; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Cloudflare MCP Asgardeo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| client | id** from the **Protocol** tab. |
{
"mcpServers": {
"math": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp-github-oauth.<your-subdomain>.workers.dev/sse"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ASGARDEO_CLIENT_ID | Configuration value read at startup. | Optional |
| ASGARDEO_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| ASGARDEO_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| COOKIE_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.