Databricks Unity Gateway
Register TrendsAGI in Unity Gateway as an external MCP server and every Databricks agent — notebooks, LangGraph, the databricks-mcp client — can read measured trend volume, velocity, insights and recommendations. One URL, one Bearer token, read-only by design.
Unity Gateway
MCPs → + MCP → Connect an existing MCP server
Server URL
https://api.trendsagi.com/mcpHTTP connection
Authorization: Bearer <TRENDSAGI_API_KEY>Unity Gateway is administrator-facing, so this is a workspace setup rather than a developer one. Nothing needs a Databricks partnership or a listing request.
The same registration is available through the CLI and SDK as create-registry-record and CreateGatewayTarget if you would rather keep it in code.
Sign in to TrendsAGI and open Profile > API Keys. Create a key named for the workspace; the agent shows you the secret once.
In the Databricks workspace, go to Unity Gateway and select MCPs, then click + MCP and choose Connect an existing MCP server.
The MCP name is permanent once created. Registering needs USE CATALOG and USE SCHEMA on the parent catalog and schema, plus CREATE SERVICE and CREATE CONNECTION on the schema.
Create a new HTTP connection with the server URL below and choose Bearer token as the authentication method, pasting the TrendsAGI API key. The workspace needs network access to api.trendsagi.com.
Call list_trends from the MCP page before you wire it into an agent. A 401 means the key is wrong or revoked; a 403 means the workspace cannot reach the host.
Use the registered MCP from notebooks, a LangGraph agent or the databricks-mcp client. Tools appear as the server's own names, so list_trends and execute_sql are called directly.
The HTTP connection accepts a TrendsAGI API key as a Bearer token. If your workspace forbids long-lived tokens, exchange the same key at the token endpoint with the client-credentials grant and cache the result.
curl -X POST https://api.trendsagi.com/oauth/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials" \
-d "client_id=databricks" \
-d "client_secret=<TRENDSAGI_API_KEY>"The returned access_token is the key itself, so rotating the key in TrendsAGI rotates the machine credential too.
Direct answers about the Unity Gateway connection, published as FAQPage structured data.
Yes. Databricks Unity Gateway registers external MCP servers through Connect an existing MCP server. You supply the Streamable HTTP URL and an HTTP connection, which can be a Bearer token, OAuth machine-to-machine or OAuth user-to-machine. TrendsAGI works with the Bearer token option today.
No. TrendsAGI accepts its API key as a Bearer token, which is the simplest HTTP connection type in Unity Gateway. If your security policy forbids long-lived tokens, the token endpoint also supports the OAuth 2.0 client_credentials grant, with the API key as the client secret.
Unity Gateway's managed OAuth covers a set of supported providers rather than arbitrary authorization servers. TrendsAGI's dynamic client registration is what MCP-native clients such as Claude Code and Cursor use; for Databricks, use the HTTP connection with a Bearer token.
Trending topics with measured volume, velocity and growth; 24-hour, 7-day and 30-day trend analytics; stored AI insights with themes, sentiment, audience and marketing angles; prioritised recommendations; crisis events on plans that include them; the watchlist; and read-only SQL over the documented tables.
Yes. Every TrendsAGI MCP tool reads. The agent cannot change your account, edit a campaign or spend money, and each call counts as one API request against your plan's daily limit.
One URL and one API key. Read-only trend data for every Databricks agent.