# How to integrate Fibery MCP with Google ADK ```json { "title": "How to integrate Fibery MCP with Google ADK", "toolkit": "Fibery", "toolkit_slug": "fibery", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/fibery/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/fibery/framework/google-adk.md", "updated_at": "2026-05-12T10:11:15.959Z" } ``` ## Introduction This guide walks you through connecting Fibery to Google ADK using the Composio tool router. By the end, you'll have a working Fibery agent that can list all open tasks for your team, fetch details for project entity by id, delete file attachment from a task through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Fibery account through Composio's Fibery MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Fibery with - [OpenAI Agents SDK](https://composio.dev/toolkits/fibery/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/fibery/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/fibery/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/fibery/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/fibery/framework/codex) - [OpenClaw](https://composio.dev/toolkits/fibery/framework/openclaw) - [Hermes](https://composio.dev/toolkits/fibery/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/fibery/framework/cli) - [LangChain](https://composio.dev/toolkits/fibery/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/fibery/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/fibery/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/fibery/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/fibery/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Fibery account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Fibery - Build an agent that connects to Fibery through MCP - Interact with Fibery using natural language ## What is Google ADK? Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol. Key features include: - Gemini Integration: Native support for Google's Gemini models - MCP Toolset: Built-in support for Model Context Protocol tools - Streamable HTTP: Connect to external services through streamable HTTP - CLI and Web UI: Run agents via command line or web interface ## What is the Fibery MCP server, and what's possible with it? The Fibery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fibery account. It provides structured and secure access to your workspace data, so your agent can perform actions like querying entities, managing custom apps, running GraphQL queries, and organizing files—all with zero manual integration code. - Entity query and retrieval: Instantly fetch detailed information or lists of entities based on type, filters, and fields, making it easy to surface project or task data as needed. - Custom app and endpoint management: Let your agent list, inspect, or delete custom apps and endpoints, streamlining workspace configuration and app lifecycle management. - Flexible data manipulation with GraphQL: Execute custom GraphQL queries and mutations against your Fibery space to fetch, update, or manipulate structured data programmatically. - File and resource cleanup: Remove outdated files or entities efficiently, helping keep your workspace organized and clutter-free with automated deletions. - Authentication and workspace insights: Validate tokens securely and retrieve workspace or app metadata, ensuring your agent always operates with up-to-date context and permissions. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FIBERY_DELETE_CUSTOM_APP_ENDPOINT` | Delete Custom App Endpoint | Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove. | | `FIBERY_DELETE_ENTITY` | Delete Entity | Permanently delete a Fibery entity by its UUID and type. Use this action when you need to remove an entity from the workspace. Requires both the entity's UUID and its full qualified type name. WARNING: Deletion is irreversible. Example: Delete a task with entity_id='550e8400-e29b-41d4-a716-446655440000' and type='Tasks/Task'. | | `FIBERY_DELETE_FILE` | Delete File | Delete a file from Fibery storage using its secret identifier. Use this action to permanently remove an uploaded file. You must provide the file's secret (fibery/secret), not its ID (fibery/id). The secret is returned when you upload a file or can be queried via the commands API. | | `FIBERY_EXECUTE_GRAPH_QL_QUERY` | Execute GraphQL Query | Execute GraphQL queries or mutations against a Fibery workspace. Fibery organizes data into Spaces, each with its own GraphQL schema containing entity types and operations. This action automatically tries common space names if no space is specified, making it easy to use without prior knowledge. Best practices: - Start with introspection queries to discover schema: { __schema { types { name } } } - Use { __type(name: "Query") { fields { name } } } to see available queries - Space names typically match your workspace app/database names - The action returns both data and errors (GraphQL can return partial results) | | `FIBERY_GET_APP_INFO` | Get App Information | Tool to retrieve application information. Use when you need the version, name, description, authentication methods, and available data sources before further operations. | | `FIBERY_GET_CUSTOM_APP_ENDPOINTS` | Get Custom App Endpoints | Tool to list custom app endpoints. Use when you need the available custom endpoints for a given app before invoking them. | | `FIBERY_GET_CUSTOM_APPS` | Get Custom Apps | Tool to list all custom apps in the Fibery workspace. Use when you need the identifiers of all custom apps. | | `FIBERY_GET_FILE` | Get File | Download a file from Fibery by its secret or ID. Use this tool to retrieve file content from Fibery storage. The file secret is a UUID that uniquely identifies a file and is the preferred identifier. You can obtain the file secret: - From the 'fibery/secret' field when querying entities that have file fields - From the 'url' field in upload file response (extract the UUID from the URL) - From rich text content where files are embedded as /api/files/{secret} | | `FIBERY_GET_GRAPH_QL_SCHEMA` | Get GraphQL Schema | Retrieves the GraphQL schema for the Fibery workspace using standard GraphQL introspection. Returns the schema as a JSON string that includes all types, queries, mutations, and their fields. Use this to discover available GraphQL operations before executing queries. | | `FIBERY_GET_USER_PREFERENCES` | Get User Preferences | Tool to retrieve the current user's UI preferences. Use after authentication to tailor UI to user settings. | | `FIBERY_POST_AUTH_REFRESH_TOKEN` | Refresh access token | Tool to validate and refresh an access token. For Fibery's standard API, this validates the current token is still working (Fibery tokens don't expire). For OAuth2 integrations with third-party services, this could be used to refresh tokens through the validate endpoint. | | `FIBERY_POST_AUTH_TOKEN` | Validate Fibery authentication and get access token | Validates Fibery API authentication and returns the active access token. This action validates that your API token is working correctly by attempting to query the Fibery API. For standard Fibery workspaces, it validates the pre-configured API token from the Authorization header. Behavior: 1. First attempts OAuth2 password grant at /auth/token (rare, only custom installations) 2. If /auth/token returns 404 (standard case), validates existing token via /commands endpoint 3. Returns the validated token that can be used for subsequent API calls The returned access_token should be used in the header: `Authorization: Token ` Note: Most Fibery workspaces use pre-generated API tokens (created in workspace settings), not username/password authentication. The username/password parameters are only used if a custom OAuth2 endpoint exists. | | `FIBERY_POST_CREATE_ENTITY` | Create Entity | Tool to create a new Fibery entity. Use when you have prepared all necessary field values and need to persist a new record. Example: Create a 'Project/Task' with title and assignee. | | `FIBERY_POST_FETCH_DATA_COUNT` | Count Entities by Type | Count the total number of entities for a given Fibery type (database). This tool queries the Fibery workspace to return how many entities exist for the specified type. Use it to get totals like "how many users", "how many features", etc. Authentication: Requires a valid Fibery API token with read access. | | `FIBERY_POST_FETCH_DATA_LIST` | Fetch Datalist Options | Fetches one page of distinct values for a specific field from a Fibery entity type. Returns a list of unique options that can be used for filtering, dropdowns, or autocomplete. ONE Fibery API call is made per invocation; pagination is caller-driven via the `offset` and `limit` request fields and the `next_offset` response field. The action first attempts the `/datalist` endpoint and, if that endpoint is unavailable on the workspace (404/405/501), falls back to a single `fibery.entity/query` command via `/commands`. | | `FIBERY_POST_FETCH_SCHEMA` | Fetch Schema | Fetch the complete schema metadata for a Fibery workspace. Returns all types (entities) and their fields, including system types (fibery/user, fibery/app) and user-defined types (MySpace/Task, etc.). Use this to discover available types before querying data or to understand the structure of your workspace. | | `FIBERY_POST_OAUTH2_ACCESS_TOKEN` | Exchange OAuth2 authorization code | Exchange an OAuth2 authorization code for access and refresh tokens. This action is used during the final step of the OAuth2 authorization code flow when building Fibery custom integration apps. After a user authorizes your app on a third-party service and is redirected back with an authorization code, use this endpoint to exchange that code for access tokens. Important: This endpoint is typically implemented by YOUR custom integration app (connector), not by Fibery itself. The action probes multiple common endpoint paths across your app's base URL and Fibery's OAuth service to maximize compatibility. Typical flow: 1. User initiates OAuth authorization via /oauth2/v1/authorize 2. User approves on the third-party service 3. Third-party redirects to callback_uri with an authorization code 4. Call THIS endpoint with the code to get access/refresh tokens | | `FIBERY_POST_REVOKE_TOKEN` | Delete/Revoke Access Token | Delete/revoke an existing Fibery API access token by its ID. Uses the DELETE /api/tokens/:token_id endpoint to permanently remove an API token. Important: This endpoint typically requires cookie-based authentication (browser session). When using API token authentication, you may receive a 401 Unauthorized error. Use this when you need to invalidate a specific API token, such as during security rotation or when revoking access for a specific integration. | | `FIBERY_POST_VALIDATE_ACCOUNT` | Validate Fibery Workspace Credentials | Validates Fibery workspace credentials by performing a test API query to retrieve the authenticated user's name. This action verifies that the provided credentials (or existing metadata credentials) are valid and have access to the workspace. Use this to confirm authentication before executing other Fibery operations. Supports multiple authentication types: workspace tokens, API keys, basic auth, and OAuth2. | | `FIBERY_POST_VALIDATE_FILTER` | Validate Filter | Validates filter definitions before executing data queries. Use this tool to verify that a filter's structure and syntax are correct without actually fetching data. For Fibery workspaces: Validates by executing a safe test query with limit=1. For custom apps: Calls the app's POST /validate/filter endpoint if available. Returns validation result indicating whether the filter can be safely used. | | `FIBERY_UPDATE_ENTITY` | Update Entity | Update an existing Fibery entity's fields. Use this to modify text fields, numbers, single-select states, workflow states, or relation fields on an entity. Prerequisites: - You need the entity's UUID (fibery/id) - obtain via Get Entities or Create Entity. - You need the fully-qualified type name (e.g., 'Engineering/Task'). - For workflow/state fields, you need the state's UUID. Limitations: - Rich text fields cannot be updated via this command. - Entity collection fields should be updated after entity creation. | | `FIBERY_UPDATE_USER_PREFERENCES` | Update User Preferences | Tool to update the current user's preferences by using the Commands API. It fetches the current user id and preferences, merges the provided payload, and writes back the merged object into 'fibery/ui-preferences' of the current fibery/user. | | `FIBERY_UPLOAD_FILE` | Upload File | Upload a file to Fibery's file storage. Use this action to upload files that can later be attached to entities or used in documents. Returns file metadata including the file ID and secret needed for subsequent operations. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Fibery MCP server is an implementation of the Model Context Protocol that connects your AI agent to Fibery. It provides structured and secure access so your agent can perform Fibery 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 Before starting, make sure you have: - A Google API key for Gemini models - A Composio account and API key - Python 3.9 or later installed - Basic familiarity with Python ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key. - Copy the key and keep it safe. You will put this in GOOGLE_API_KEY. Composio API Key and User ID - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY. - Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Fibery via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables Save all your credentials in the .env file. What's happening: - GOOGLE_API_KEY authenticates with Google's Gemini models - COMPOSIO_API_KEY authenticates with Composio - COMPOSIO_USER_ID identifies the user for session management ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate environment What's happening: - os reads environment variables - Composio is the main Composio SDK client - GoogleProvider declares that you are using Google ADK as the agent runtime - Agent is the Google ADK LLM agent class - McpToolset lets the ADK agent call MCP tools over HTTP ```python import os import warnings from composio import Composio from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") ``` ### 6. Create Composio client and Tool Router session What's happening: - Authenticates to Composio with your API key - Declares Google ADK as the provider - Spins up a short-lived MCP endpoint for your user and selected toolkit - Stores the MCP HTTP URL for the ADK MCP integration ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["fibery"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent What's happening: - Connects the ADK agent to the Composio MCP endpoint through McpToolset - Uses Gemini as the model powering the agent - Lists exact tool names in instruction to reduce misnamed tool calls ```python composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Fibery operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening: - adk run runs the agent in CLI mode - adk web . opens a web UI for interactive testing ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```python import os import warnings from composio import Composio from composio_google import GoogleProvider from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider()) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["fibery"], ) COMPOSIO_MCP_URL = composio_session.mcp.url composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Fibery operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Fibery with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Fibery using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Fibery tools - Environment variables keep your credentials secure and separate from code - Clear agent instructions reduce tool calling errors - The ADK web UI provides an interactive interface for testing and development You can extend this setup by adding more toolkits to the toolkits array in your session configuration. ## How to build Fibery MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/fibery/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/fibery/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/fibery/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/fibery/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/fibery/framework/codex) - [OpenClaw](https://composio.dev/toolkits/fibery/framework/openclaw) - [Hermes](https://composio.dev/toolkits/fibery/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/fibery/framework/cli) - [LangChain](https://composio.dev/toolkits/fibery/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/fibery/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/fibery/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/fibery/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/fibery/framework/crew-ai) ## Related Toolkits - [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [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. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives. - [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page. - [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes. - [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights. - [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Fibery MCP? With a standalone Fibery MCP server, the agents and LLMs can only access a fixed set of Fibery tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Fibery and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Google ADK? Yes, you can. Google ADK 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 Fibery tools. ### Can I manage the permissions and scopes for Fibery while using Tool Router? Yes, absolutely. You can configure which Fibery 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 Fibery data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)