Choose Your Integration

Nimble offers four integration paths. All four reach the same APIs. The right one depends on where your agent runs and how you want to authenticate.

Pick a path

Path	Best for	Auth	Start here
MCP server	Chat assistants and production agents	OAuth sign-in, or an API key	MCP Server
Plugin + Skills	Coding agents with terminal access	OAuth sign-in, or `NIMBLE_API_KEY`	Plugin Installation
SDK + CLI	Application code that needs full control	`NIMBLE_API_KEY`	Installation
Warehouse apps	Data teams working in SQL	API key held in the warehouse	Databricks, Snowflake

Prefer OAuth where the client supports it. You sign in through the browser once and never handle a key, so there is nothing to paste, rotate, or leak. Tokens refresh automatically and you can revoke access at any time.

Which path fits?

Coding agent
Chat assistant
Building an app
Warehouse or SQL

Install the plugin.If your agent runs in a terminal, the plugin is the most complete setup. It installs two things at once: Agent Skills, which teach your agent which Nimble product fits a given job, and a pre-configured MCP server connection.Skills matter more than they sound. Without them an agent knows the API exists but not when to reach for Extract Templates instead of Extract, or a Web Search Agent instead of Search. The skills encode those choices.Plugin Installation has a tab for each supported platform: Claude Code, Claude Cowork, Cursor, Codex, Cortex Code, and Vercel CLI.For any other terminal agent, install the CLI and set NIMBLE_API_KEY. The CLI reaches every product, including several the MCP server does not carry. See the coverage table below.

Use the MCP server, and sign in with OAuth.Chat assistants like Claude have no terminal, so they cannot run the CLI. They connect to outside tools over MCP instead.Where the client supports OAuth, there is no key to handle at all. Click connect, approve the scopes in your browser, and the client stores and refreshes the token for you.

Client	Setup
Claude Chat & CoWork	Claude Connectors
VS Code and GitHub Copilot	Azure MCP Center
Microsoft Copilot Studio	Copilot Studio
Snowflake CoWork	Cortex Agents

For clients without OAuth support, point them at the server and pass a key instead:

{
  "mcpServers": {
    "nimble": {
      "type": "http",
      "url": "https://mcp.nimbleway.com/mcp",
      "headers": { "Authorization": "Bearer NIMBLE_API_KEY" }
    }
  }
}

See MCP Server for Claude Desktop, Cursor, and other clients.

Start with MCP for speed. Move to the SDK when you need control.Both paths are production-ready, and they are not exclusive. Many teams start with MCP, then move specific tools to the SDK as requirements tighten.MCP, fastest to ship. OpenAI and Anthropic both accept a hosted MCP server URL directly in their APIs. Your model gets tool calling with no schemas to write or maintain.SDK, full control. Use the SDK when you need custom tool schemas, your own response shaping, or a product the MCP server does not carry.

Framework	Guide
OpenAI	OpenAI connector
Anthropic	Anthropic SDK
LangChain	LangChain
LlamaIndex	LlamaIndex
Vercel AI SDK	Vercel AI SDK
Google ADK	Google ADK
Any framework	Python, Node, or Go

Install the warehouse app and call the web from SQL.Nimble runs inside Databricks and Snowflake. Your API key stays in the warehouse, and results land as rows. No pipeline to build and no data leaves your account on the way in.

Warehouse	Options
Databricks	Marketplace MCP, Genie, Data enrichment
Snowflake	Native App, Cortex Agents, Data enrichment

Snowflake reads your key from a Snowflake Secret you control. Databricks takes it as a bearer token.

What each path can reach

Coverage is not equal. Pick a path that carries the products you need.

Product	Skills	MCP	SDK	CLI
Search	Yes	Yes	Yes	Yes
Extract	Yes	Yes	Yes	Yes
Extract Templates	Yes	Yes	Yes	Yes
Map	Yes	Yes	Yes	Yes
Crawl	Yes	Yes	Yes	Yes
Web Search Agents	Yes	Yes	Yes	Yes
SERP	No	No	Yes	Yes
Media	No	No	Yes	Yes
Domain Knowledge	No	No	Yes	Yes
Jobs	No	No	Yes	Yes

Authentication

Two mechanisms cover every path. Use OAuth where you can and an API key where you must. The MCP server supports OAuth 2.1 with PKCE. Nothing to configure: the client discovers the flow from the server, opens your browser, and stores the token itself.


Scopes	`nimble:read`, `nimble:write`, `offline_access`, `openid`
Refresh	Handled by the client. `offline_access` keeps access alive between sessions.
Revoke	Disconnect from the client, or revoke from your Nimble account.
Works with	Claude, VS Code and GitHub Copilot, Copilot Studio, Cortex Code

Approving the consent screen grants permission to verify your identity, search the web, extract data, and manage Web Search Agents.

API key

Path	How it works
SDK + CLI	Set `NIMBLE_API_KEY`, or pass the key to the client constructor.
MCP server	Pass the key as `Authorization: Bearer <key>` for clients without OAuth.
Plugin + Skills	Set `NIMBLE_API_KEY`. The CLI and skills read it automatically.
Warehouse	Snowflake reads a Snowflake Secret. Databricks takes a bearer token.
Proxy	Credentials go in the connection string, not a header. See Proxy authentication.

Get a key from Settings → API Keys. Issue a separate key per project so you can revoke one without breaking the rest.

Using more than one path

Most teams do. A plugin for local development, MCP for a chat assistant, and the SDK for production code all hit the same APIs with the same key.

Next steps

Plugin Installation

Install skills and MCP config in your coding agent

MCP Server

Give any AI agent live web access

Quickstart

Your first API call in under a minute

Connectors

Wire Nimble into your agent framework

​Pick a path

​Which path fits?

​What each path can reach

​Authentication

​OAuth sign-in

​API key

​Using more than one path

​Next steps

Plugin Installation

MCP Server

Quickstart

Connectors

Pick a path

Which path fits?

What each path can reach

Authentication

OAuth sign-in

API key

Using more than one path

Next steps