Create via Dashboard

Outcomes

Create and configure an Gateway using the Arcade dashboard with full control over settings.

Prerequisites

Create an Arcade

Create a Gateway

To create an Gateway, go to the MCP Gateways dashboard and click the “Create ” button.

When configuring an Gateway, you can select the tools you want to include in the Gateway from any available to the :

Configuration Options

The options available when configuring an Gateway are:

Name: The name of the Gateway. Informative only.
Description: The description of the Gateway. This is useful for humans and some MCP clients may surface this information to the .
LLM Instructions: Optional instructions for the LLM about how to use the Gateway.
Slug: The slug of the Gateway. This is the URL slug that will be used to access the . It must be unique.
Authentication: How end users authenticate to the gateway. Users will still need to authenticate to the tools within the Gateway as normal. The form asks “Who are the of this Gateway?” with two top-level choices:
- Members of this (Arcade Auth): End users sign in with Arcade as members of this project. Recommended for development, testing, and internal use when every end is already a member.
- Non-Arcade : End users come from outside Arcade. Pick one of:
  - (recommended): Arcade redirects end users to your OIDC identity provider to sign in. Pick this for production whose end have identities in your own OIDC identity system. See User Sources for how to set one up.
  - Arcade Headers (fallback): The client passes an key in the Authorization header and the end ’s ID in the Arcade-User-ID header. Pick this for clients that can’t run a browser-based OAuth flow.
Allowed : A selection of tools in the Arcade Tool Catalog that will be available to the Gateway.

When an end signs in to a gateway, Arcade shows an OAuth consent screen before issuing a token. The Skip consent for trusted clients (optional) field on the gateway form lets you allowlist specific client IDs that should bypass that consent screen. End users connecting through an allowlisted client go straight from sign-in to a working session.

The field is available on gateways that use Arcade Auth or a . It does not apply to Arcade Headers.

A client ID is what the client sends to Arcade during OAuth registration. Most MCP clients today perform Dynamic Client Registration , which mints a fresh, per-installation client ID that’s not useful for an allowlist. Clients that publish a Client ID Metadata Document (CIMD) use their published HTTPS URL as a stable client ID — that URL is what goes in the allowlist.

Known MCP client IDs

MCP client	Client ID
Claude (Claude Desktop and Claude.ai)	`https://claude.ai/oauth/mcp-oauth-client-metadata`
Claude Code	`https://claude.ai/oauth/claude-code-client-metadata`
Visual Studio Code	`https://vscode.dev/oauth/client-metadata.json`

This list is intentionally short. The CIMD ecosystem is early as of May 2026, so most other clients (Cursor, GitHub Copilot, Codex, and others) do not yet publish a stable client ID that can be allowlisted. We expect this list to grow as those clients add CIMD support.

Find the client ID for an unlisted client

If the client publishes a CIMD, its documentation will reference an https://...client-metadata URL or similar. That URL is the client ID — paste it into the allowlist as-is.

If the client uses Dynamic Client Registration, the client ID is generated per registration and changes any time the client re-registers. You’d need to track the latest registered client ID against your gateway, which usually isn’t worth the operational cost. Wait until the client adopts CIMD instead.

After Creating a Gateway

Once you’ve created a gateway, you’ll need to add it to your chat client. The assistant will provide the URL (for example, https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>).

See Connect to MCP clients for setup instructions specific to your client.