{
  "schema_version": 2,
  "id": "operate/iris/context-gateway/manage-gateway",
  "title": "View and manage a Context Gateway",
  "url": "https://redis.io/docs/latest/operate/iris/context-gateway/manage-gateway/",
  "summary": "View and manage a Context Gateway and its Upstreams in Redis Cloud.",
  "aliases": [
    "/operate/iris/context-retriever/view-service/",
    "/operate/iris/context-retriever/view-admin-keys/"
  ],
  "tags": [
    "docs",
    "operate",
    "iris"
  ],
  "last_updated": "2026-10-30T12:43:13-07:00",
  "page_type": "content",
  "content_hash": "6679be7250d2139583a0de3fa9c7c98761b72b2a2beba2287e9f472debf156e2",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "After you [create a Context Gateway](https://redis.io/docs/latest/operate/iris/context-gateway/create-gateway), select **Context Gateways** under **Iris** in the Redis Cloud console menu to see the list of your Gateways.\n\nThe list shows each Gateway's **Name**, its **Tool exposure** mode, and its **Created date**. Select a Gateway to open it.\n\n\n\nThe Gateway's page has the **Configuration** and **Upstreams** tabs, and opens on the **Configuration** tab."
    },
    {
      "id": "configuration-tab",
      "title": "Configuration tab",
      "role": "configuration",
      "text": "The **Configuration** tab starts with a banner for connecting agents. Select **Connect** or **Create API key** there to [connect an agent](https://redis.io/docs/latest/operate/iris/context-gateway/create-gateway#connect-an-agent).\n\nThe **General settings** section shows the Gateway's **Gateway ID**, its Model Context Protocol (MCP) endpoint (**MCP endpoint**), its **Created date**, and its **Configuration updated date**. To change a setting, select **Edit**, make your changes, and select **Save changes**.\n\n| Setting | Description |\n|:--------|:------------|\n| **Name** | The Gateway's name, up to 128 characters. |\n| **Description** | An optional description. |\n| **Tool exposure** | **Search** or **Full**. Agents get the new mode on their next request. With many tools, full mode fills more of their context. |\n\nIf someone else changed the Gateway while you were editing, the console asks you to reload it and apply your changes again. If the Gateway is in search mode and serves only a few tools, the tab suggests full mode."
    },
    {
      "id": "delete-a-gateway",
      "title": "Delete a Gateway",
      "role": "content",
      "text": "Deleting a Gateway removes its MCP endpoint, and agents that use it lose access right away. You can't delete a Gateway that has Upstreams, because deleting a Gateway never deletes its Upstreams for you. [Delete its Upstreams](#delete-an-upstream) first. Until you do, the **Danger zone** section lists them.\n\n1. On the Gateway's **Configuration** tab, select **Delete gateway** in the **Danger zone** section.\n1. Select the **Yes, I want to delete this resource** checkbox.\n1. Select **Delete gateway**.\n\nThis action can't be undone."
    },
    {
      "id": "upstreams-tab",
      "title": "Upstreams tab",
      "role": "content",
      "text": "The **Upstreams** tab lists the Gateway's Upstreams, with each one's **Name**, **Namespace**, **Type** (**MCP server** or **Context Surface**), number of **Tools**, whether it's **Enabled**, and its **Created date**.\n\nFrom this tab, you can:\n\n- [Add an MCP server](https://redis.io/docs/latest/operate/iris/context-gateway/create-gateway#add-an-mcp-server) or [create a Context Surface](https://redis.io/docs/latest/operate/iris/context-gateway/create-gateway#create-a-context-surface).\n- Turn an Upstream on or off with its **Enabled** switch. A disabled Upstream keeps its configuration and tools, but agents see none of its tools.\n- Use an Upstream's actions menu to open, refresh, enable or disable, or delete it.\n\nSelect an Upstream to open its page, which has the **Configuration** and **Tools** tabs and opens on the **Configuration** tab."
    },
    {
      "id": "refresh-an-upstream",
      "title": "Refresh an Upstream",
      "role": "content",
      "text": "Select **Refresh** on an Upstream to discover an MCP server's tools again, or to regenerate a Context Surface's tools. Refresh after the server's tools change, or after you fix a problem that stopped discovery. If the refresh fails, the console shows the error and how to fix it."
    },
    {
      "id": "tools-tab",
      "title": "Tools tab",
      "role": "content",
      "text": "The **Tools** tab lists the Upstream's tools by their `namespace.tool` names, with each tool's description and annotations, such as **Read-only** or **Destructive**.\n\nThe tab also shows each tool's **Cache** and **Compression** policy. You can't change these policies in the console.\n\n\nFor a Context Surface, the **Entities** section shows its data model. Select **Edit data model** to change it. Saving regenerates the Surface's tools and removes the policies of any tools the new model drops."
    },
    {
      "id": "configuration-tab-1",
      "title": "Configuration tab",
      "role": "configuration",
      "text": "The **Configuration** tab shows the Upstream's settings and its **Upstream ID**. In the **General** section, select **Edit name** to rename the Upstream, or use the **Status** switch to turn it on or off.\n\n- For an MCP server, select **Edit MCP server** to change the **Endpoint URL** and the authentication. When you change the endpoint, enter every secret again, so the Gateway never sends credentials to a host you didn't intend. Saving discovers the server's tools again.\n- For a Context Surface, you can replace the data model from a JavaScript Object Notation (JSON) file with **Replace from JSON**. Replacing the data model regenerates the Surface's tools.\n\nYou can't change an Upstream's namespace, or a Context Surface's **Surface database ID**, after you create it."
    },
    {
      "id": "delete-an-upstream",
      "title": "Delete an Upstream",
      "role": "content",
      "text": "Deleting an Upstream removes its tools from the Gateway right away, along with their tool policies.\n\n1. On the Upstream's **Configuration** tab, select **Delete Upstream** in the **Danger zone** section. **Delete** in the Upstream's actions menu on the **Upstreams** tab opens the same step.\n1. Select the **Yes, I want to delete this resource** checkbox.\n1. Select **Delete Upstream**.\n\nWhen you delete a Context Surface, the Gateway also drops the search indexes it built on the Surface database. Your records stay. If the Gateway can't drop the indexes, you can retry once the database is fixed, or select **Delete anyway**. Then indexes named `idx:<upstream-id>:*` stay on the database until someone drops them."
    }
  ],
  "examples": []
}