How to integrate Influxdb cloud MCP with Pydantic AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Influxdb cloud Logo
Pydantic AI Logo
divider

Introduction

This guide walks you through connecting Influxdb cloud to Pydantic AI using the Composio tool router. By the end, you'll have a working Influxdb cloud agent that can write temperature sensor data to bucket, add cpu usage graph to dashboard, update retention policy for analytics data, list all available api routes for instance through natural language commands.

This guide will help you understand how to give your Pydantic AI agent real control over a Influxdb cloud account through Composio's Influxdb cloud MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Influxdb cloud
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Influxdb cloud workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

What is the Influxdb cloud MCP server, and what's possible with it?

The Influxdb cloud MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your InfluxDB Cloud account. It provides structured and secure access to your time series data, letting your agent run queries, ingest new data, manage dashboards, and update user settings automatically.

  • Real-time data ingestion and writing: Instantly send line protocol data points to your InfluxDB Cloud buckets for seamless time series collection and analytics.
  • Automated dashboard cell management: Direct your agent to add new cells to existing dashboards, making it easy to visualize and monitor the latest metrics or results.
  • Advanced query analysis and validation: Have the agent generate and inspect Flux query Abstract Syntax Trees (AST) to validate and debug your analytics scripts before running them.
  • User and session management: Enable your agent to sign users in or out and even delete users by ID, supporting secure and automated access control.
  • DBRP mapping updates and retrieval: Let your agent fetch or update Database Retention Policy (DBRP) mappings, so you can adapt your data retention and default policies on the fly.

Supported Tools & Triggers

Tools
Add Dashboard CellTool to add a cell to a dashboard.
Delete UserTool to delete a user by ID.
Generate Flux Query ASTTool to generate a Flux query Abstract Syntax Tree (AST).
Get DBRP MappingTool to retrieve a DBRP mapping by ID.
List RoutesTool to list top-level API routes.
Sign InTool to create a user session by authenticating credentials.
Sign OutTool to expire a user session using a session cookie.
Update DBRPTool to update a DBRP mapping's default and retention policy.
Write Line Protocol DataTool to write line protocol data to a bucket.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Influxdb cloud
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Influxdb cloud
  • MCPServerStreamableHTTP connects to the Influxdb cloud MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Influxdb cloud
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["influxdb_cloud"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Influxdb cloud tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
influxdb_cloud_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[influxdb_cloud_mcp],
    instructions=(
        "You are a Influxdb cloud assistant. Use Influxdb cloud tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Influxdb cloud endpoint
  • The agent uses GPT-5 to interpret user commands and perform Influxdb cloud operations
  • The instructions field defines the agent's role and behavior

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Influxdb cloud.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Influxdb cloud API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Influxdb cloud and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Influxdb cloud
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["influxdb_cloud"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    influxdb_cloud_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[influxdb_cloud_mcp],
        instructions=(
            "You are a Influxdb cloud assistant. Use Influxdb cloud tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Influxdb cloud.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with Influxdb cloud through Composio's Tool Router. With this setup, your agent can perform real Influxdb cloud actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Influxdb cloud for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

How to build Influxdb cloud MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Influxdb cloud MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Influxdb cloud MCP with Claude Agent SDK

Google ADK

Google ADK

Use Influxdb cloud MCP with Google ADK

LangChain

LangChain

Use Influxdb cloud MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Influxdb cloud MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Influxdb cloud MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Influxdb cloud MCP with LlamaIndex

CrewAI

CrewAI

Use Influxdb cloud MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Influxdb cloud MCP?

With a standalone Influxdb cloud MCP server, the agents and LLMs can only access a fixed set of Influxdb cloud tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Influxdb cloud and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Pydantic AI?

Yes, you can. Pydantic AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Influxdb cloud tools.

Can I manage the permissions and scopes for Influxdb cloud while using Tool Router?

Yes, absolutely. You can configure which Influxdb cloud scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Influxdb cloud data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free