# How to integrate Fluxguard MCP with LangChain

```json
{
  "title": "How to integrate Fluxguard MCP with LangChain",
  "toolkit": "Fluxguard",
  "toolkit_slug": "fluxguard",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/fluxguard/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/fluxguard/framework/langchain.md",
  "updated_at": "2026-05-12T10:11:58.419Z"
}
```

## Introduction

This guide walks you through connecting Fluxguard to LangChain using the Composio tool router. By the end, you'll have a working Fluxguard agent that can add competitor's homepage for daily monitoring, list all recent alerts for your sites, acknowledge today's website change alert through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Fluxguard account through Composio's Fluxguard MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Fluxguard with

- [OpenAI Agents SDK](https://composio.dev/toolkits/fluxguard/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/fluxguard/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/fluxguard/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/fluxguard/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/fluxguard/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/fluxguard/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/fluxguard/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/fluxguard/framework/cli)
- [Google ADK](https://composio.dev/toolkits/fluxguard/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/fluxguard/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/fluxguard/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/fluxguard/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/fluxguard/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Fluxguard project to Composio
- Create a Tool Router MCP session for Fluxguard
- Initialize an MCP client and retrieve Fluxguard tools
- Build a LangChain agent that can interact with Fluxguard
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

## What is the Fluxguard MCP server, and what's possible with it?

The Fluxguard MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fluxguard account. It provides structured and secure access to your website monitoring and alerting data, so your agent can perform actions like adding new monitored pages, categorizing sites, retrieving alerts, acknowledging changes, and managing webhooks on your behalf.
- Automated website monitoring setup: Direct your agent to add new web pages or entire sites for continuous change detection and tracking with just a quick prompt.
- Alert retrieval and analysis: Have your agent fetch detailed information about recent alerts, surfacing critical changes on any monitored page instantly.
- Intelligent alert acknowledgment: Let your agent acknowledge and mark alerts as reviewed, helping your team stay organized and responsive.
- Site and category management: Organize your monitored properties by creating, updating, or deleting site categories to keep your web asset monitoring streamlined.
- Webhook automation: Set up or remove webhooks to automate notifications, ensuring you never miss an important website change event.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `FLUXGUARD_ADD_PAGE` | Add FluxGuard Page | Tool to add a new page for monitoring in FluxGuard. This action can: 1. Create a new site with a page (when siteId/sessionId are not provided) 2. Add a page to an existing site (when siteId/sessionId are provided) When creating a new site, you can optionally assign it to categories and provide a nickname. Use this when you need to start monitoring a URL for changes. |
| `FLUXGUARD_CREATE_SITE_CATEGORY` | Create FluxGuard Site Category | Creates a new site category in FluxGuard for organizing monitored websites. Site categories help you group and manage your monitored sites logically (e.g., by environment like 'Production' or 'Staging', by purpose like 'Marketing' or 'E-commerce', or by client/team). Use this action to create categories before adding sites, making it easier to filter and organize your monitoring dashboard. The returned category ID can be used when adding sites to assign them to this category. |
| `FLUXGUARD_CREATE_WEBHOOK` | Create Webhook | Creates a webhook endpoint registration in FluxGuard to receive real-time notifications when changes are detected on monitored pages. When changes occur, FluxGuard will POST JSON data to your specified URL containing change details, diff information, and file references. Use this when you need to integrate FluxGuard change detection into your own systems, automation workflows, or alerting infrastructure. Note: Only one webhook can be active per account. Creating a new webhook will replace any existing webhook configuration. |
| `FLUXGUARD_DELETE_PAGE` | Delete Fluxguard Page | Permanently deletes a monitored page from FluxGuard along with all its captured snapshots and version history. This is a destructive operation that cannot be undone. Use this when you need to remove a page that is no longer needed for monitoring. The operation is idempotent - deleting an already-deleted page will succeed without error. To obtain the required IDs (site_id, session_id, page_id), first use FLUXGUARD_ADD_PAGE to create a page or FLUXGUARD_GET_SITES to list existing sites and their pages. |
| `FLUXGUARD_DELETE_SITE` | Delete Fluxguard Site | Permanently deletes a monitored site and all associated data including sessions, pages, and captured versions. This operation is idempotent - deleting a non-existent site returns success. Use when you need to remove a site from FluxGuard monitoring. |
| `FLUXGUARD_DELETE_WEBHOOK` | Delete Webhook | Permanently removes a webhook from your FluxGuard account by its ID. After deletion, the webhook will no longer receive notifications about monitored page changes. This operation is idempotent - deleting a non-existent webhook will succeed without error. Use this tool when you need to remove a webhook configuration that is no longer needed. |
| `FLUXGUARD_GET_ALL_CATEGORIES` | Get All FluxGuard Categories | Retrieves all categories defined in your FluxGuard account. Use this tool when you need to: - List all available categories for organizing sites or pages - Get category IDs for use in other operations - Check what categories exist before creating new ones This is a read-only operation that returns both site and page categories. No parameters are required - simply call this action to get all categories. |
| `FLUXGUARD_GET_PAGE_DATA` | Get FluxGuard Page Data | Tool to retrieve comprehensive data for a monitored page in FluxGuard. This action fetches detailed information about a specific page including its URL, monitoring status, capture history, and metadata. Use this when you need to verify a page exists, check its monitoring status, or retrieve page configuration details. The page must be identified by its site_id, session_id, and page_id, which are typically obtained from FLUXGUARD_ADD_PAGE when creating a page or from FLUXGUARD_GET_SITES when listing existing sites and their pages. |
| `FLUXGUARD_GET_SAMPLE_WEBHOOK` | Get Sample Webhook Payload | Tool to retrieve a sample webhook payload. Use when you need to inspect the structure of webhook notifications. |
| `FLUXGUARD_GET_USER` | Get Current FluxGuard Account | Retrieves the authenticated FluxGuard account's information as a user profile. Returns details about the current organization's account including ID, status, creation date, and last update timestamp. This provides account information in a user-friendly format for the authenticated API key's organization. |
| `FLUXGUARD_GET_WEBHOOKS` | Get FluxGuard Webhooks | Retrieves all configured webhooks for the FluxGuard account. Use this action to list all webhook endpoints that are configured to receive FluxGuard change notifications. Each webhook includes its URL, secret for signature verification, API version, and associated site categories. No parameters required - returns all webhooks for the authenticated account. |
| `FLUXGUARD_INITIATE_CRAWL` | Initiate FluxGuard Crawl | Tool to initiate a crawl for a session identified by siteId and sessionId. Use when you need to start monitoring a site for changes after adding pages with FLUXGUARD_ADD_PAGE. |
| `FLUXGUARD_WEBHOOK_NOTIFICATION` | Fluxguard Webhook Notification | Simulate Fluxguard webhook notification by sending change detection data to your webhook endpoint. Use this tool to test your webhook receiver implementation by sending it a properly formatted Fluxguard webhook payload with optional HMAC signature authentication. This helps verify your endpoint can receive and process Fluxguard change notifications correctly. Note: This does NOT retrieve data from Fluxguard or trigger actual monitoring - it only sends test notifications to your webhook URL. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Fluxguard MCP server is an implementation of the Model Context Protocol that connects your AI agent to Fluxguard. It provides structured and secure access so your agent can perform Fluxguard operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Fluxguard tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Fluxguard 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
- This approach allows the agent to dynamically load and use Fluxguard tools as needed
```python
# Create Tool Router session for Fluxguard
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['fluxguard']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['fluxguard']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "fluxguard-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "fluxguard-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Fluxguard related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Fluxguard related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['fluxguard']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "fluxguard-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Fluxguard related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

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

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['fluxguard']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "fluxguard-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Fluxguard related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Conclusion

You've successfully built a LangChain agent that can interact with Fluxguard through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Fluxguard MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/fluxguard/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/fluxguard/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/fluxguard/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/fluxguard/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/fluxguard/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/fluxguard/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/fluxguard/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/fluxguard/framework/cli)
- [Google ADK](https://composio.dev/toolkits/fluxguard/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/fluxguard/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/fluxguard/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/fluxguard/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/fluxguard/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Codereadr](https://composio.dev/toolkits/codereadr) - Codereadr is a mobile platform for barcode scanning and data collection. It helps businesses securely capture, validate, and report field data with ease.
- [Coinmarketcap](https://composio.dev/toolkits/coinmarketcap) - Coinmarketcap is a leading cryptocurrency data platform offering real-time and historical market data on digital coins and exchanges. It empowers users to track prices, volumes, and trends for smarter crypto decisions.
- [College football data](https://composio.dev/toolkits/college_football_data) - College football data delivers comprehensive NCAA football stats, scores, and recruiting details via API. Get real-time, historical, and advanced analytics for teams, games, and players.
- [Corrently](https://composio.dev/toolkits/corrently) - Corrently delivers real-time and forecasted renewable energy, CO₂, and electricity pricing data via API. It helps users make smarter, greener energy decisions and lower their carbon footprint.
- [Currents api](https://composio.dev/toolkits/currents_api) - Currents News API delivers real-time news articles from global sources in multiple languages and categories. Get instant access to diverse news feeds for deeper insights and timely updates.
- [Dadata ru](https://composio.dev/toolkits/dadata_ru) - Dadata ru is a data validation and enrichment API for Russian addresses, companies, and personal data. It helps automate data entry, reduce errors, and standardize records across your workflows.
- [Data247](https://composio.dev/toolkits/data247) - Data247 is a secure, on-demand platform for business data lookups. It helps you quickly access, validate, and enrich critical business data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Fluxguard MCP?

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

### Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain 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 Fluxguard tools.

### Can I manage the permissions and scopes for Fluxguard while using Tool Router?

Yes, absolutely. You can configure which Fluxguard 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 Fluxguard data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)