Connect AI agents to Devgate

Connect with OAuth

Use OAuth when your client supports MCP authentication and dynamic client registration. No API key is copied into the client.

1. Open your client's connectors, integrations, or MCP settings and add a remote server.
2. Enter https://muslimdevgate.com/api/mcp as the server URL.
3. Choose OAuth or automatic registration. Sign in to Devgate when your browser opens, then authorize the connection.
4. Confirm that the client discovers 55 tools. Discovery through tools/list does not consume API quota.

The connector receives short-lived access tokens and rotating refresh tokens scoped to quran:read. Tool calls use your account quota and appear in usage history. Revoke the managed connector credential at any time from API keys.

Connect with an API key

For agents that support custom headers instead of OAuth, create a credential in API keys and use this Streamable HTTP configuration.

{
  "mcpServers": {
    "devgate": {
      "type": "http",
      "url": "https://muslimdevgate.com/api/mcp",
      "headers": {
        "Authorization": "Bearer k-mdevg-YOUR_KEY"
      }
    }
  }
}

If the client asks for fields instead of JSON, use https://muslimdevgate.com/api/mcp as the server URL and Bearer k-mdevg-YOUR_KEY as the Authorization header. Never place a real key in source control, logs, screenshots, prompts, or shared configuration.

Behavior and limits

• Complete-Quran and complete-tafsir tools can return large results. Prefer focused ayah, surah, and tafsir tools unless the complete document is required.
• Tool results preserve upstream JSON as structured content; the server does not silently summarize or substitute the requested data.