Skip to main content
Give agents on Oracle Cloud Infrastructure (OCI) live web data from Nimble. There are two ways in, and both use the same Nimble API key.

Prerequisites

  • A Nimble API key from the Nimble dashboard. A free trial is available.
  • An OCI tenancy.
  • For the chat agent: git, python3, and zip on your machine, and rights to create IAM policies in the tenancy. See Fill in the pack settings if you lack them.
  • For MCP: an OCI Generative AI project, an OCI Generative AI API key, and an IAM policy that grants the key access. The setup step links Oracle’s guide.

Deploy the Managed Enterprise Chat Agent

The OCI AI Accelerator Starter Packs are Terraform stacks from Oracle. They deploy complete AI apps onto Oracle Kubernetes Engine (OKE). The Managed Enterprise Chat Agent pack (paas_rag) is an enterprise chat app. It answers questions over your uploaded documents with citations, using OCI Generative AI models and Oracle 26ai as the vector store. It needs no GPUs. Nimble is the pack’s built-in web search provider. Add your Nimble API key at deploy time and the pack’s backend answers web search requests with Nimble.
The Nimble setting was added after Oracle’s latest published release. The v0.0.8_paas_rag.zip on the Releases page does not include it. Build the stack zip from the repository’s main branch, as shown below, until a newer release ships.
1

Build the stack zip

Clone the repository, generate the schema for the paas_rag pack, and zip the Terraform folder:
2

Create the stack in OCI Resource Manager

In the OCI Console, go to Developer Services → Resource Manager → Stacks. Pick your compartment, click Create Stack, select .zip file, and upload paas_rag.zip. Click Next.
3

Fill in the pack settings

The form groups settings by section. These are the ones that matter for this pack:The Nimbleway API Key field is optional. Leave it blank and web search is unavailable.Create IAM Policies, under Advanced Options, is on by default and writes policies at the tenancy root. That needs tenancy-admin rights. Without them, uncheck it and have an admin apply Oracle’s IAM policies first.
By default the stack deploys a public URL, and the API behind it requires no login. Anyone with the URL can run web searches on your Nimble key, use your OCI Generative AI quota, and read uploaded documents. For anything beyond a short test, check Deploy Private K8s and Load Balancer under Advanced Options, or restrict ingress by IP.
4

Apply the stack

Click Next → Run apply → Create. Deployment takes roughly 20 to 40 minutes. When it finishes, the stack’s Outputs tab shows the chat app’s address as RAG Service URL.To stop all charges later, open the stack and click Destroy.

What the Nimble setting does

The pack runs OGX, the open agentic API server, as its backend. Your API key is passed to OGX’s remote::nimble-search provider, which is the pack’s only web search backend. Any web_search tool call the backend handles goes to Nimble Search. The stack ships with this provider configuration:
max_results: 3 and search_depth: lite keep searches fast by default: titles, URLs, and snippets for the top three results. To change them, edit ai-accelerator-tf/files/llamastack_paas_config.yaml before you build the zip. See the OGX page for every option.
Terraform users can set the key as the nimbleway_api_key variable instead of using the console form. It is marked sensitive, so Terraform does not print it.

Connect Nimble MCP to OCI Generative AI

OCI Generative AI serves an OpenAI-compatible Responses API. It supports MCP calling: OCI connects to a remote MCP server directly, with no tool-calling loop in your code. Point it at Nimble’s hosted MCP server and OCI models that support the Responses API can search and extract the web. Set three environment variables before you run the example:

Example Request

Any OpenAI-compatible client works the same way. The TypeScript example uses top-level await, so run it as an ES module.

How it works

1

Set up OCI Generative AI

In the OCI Console, create a Generative AI project and an API key in the same region. Grant the key permission with an IAM policy. Oracle’s quick start walks through all three.
2

Add Nimble as an mcp tool

Set server_url to https://mcp.nimbleway.com/mcp and put your Nimble API key in authorization. Pass the raw key, with no Bearer prefix.
3

OCI calls Nimble for you

When the model decides it needs the web, OCI calls the Nimble tool directly and feeds the results back to the model. Your code receives the final, grounded answer.

Parameters

https://inference.generativeai.<region>.oci.oraclecloud.com/openai/v1. Use the region where your project and API key live, for example us-chicago-1 or us-ashburn-1.
Required. The OCID of your OCI Generative AI project, which starts with ocid1.generativeaiproject. The OpenAI SDK sends it as the OpenAI-Project header.
Required. Your Nimble API key, with no Bearer prefix. Oracle states that OCI does not store or log MCP authorization tokens.
Optional. Limits which Nimble tools the model sees. Fewer tools means a shorter prompt, lower cost, and faster responses. Keep it set. Without it, the model also sees tools that start paid crawls or delete Web Search Agents. With require_approval: never, those run without confirmation. See the MCP server docs for what each product covers.
Optional. Set to never so OCI runs Nimble tools without pausing for approval.
Required. Any OCI Generative AI model that supports the Responses API, such as openai.gpt-oss-120b. Meta models do not support the Responses API.

Resources

OGX

The agentic API server behind the chat agent, and its Nimble provider settings.

Nimble MCP Server

Tools, authentication, and setup for other MCP clients.

OCI AI Accelerator Starter Packs

Oracle’s Terraform stacks, including the Managed Enterprise Chat Agent.

MCP calling in OCI Generative AI

Oracle’s reference for remote MCP tools in the Responses API.