How to integrate Productlane MCP with Google ADK

This guide walks you through connecting Productlane to Google ADK using the Composio tool router. By the end, you'll have a working Productlane agent that can open productlane widget for user feedback, display specific docs article in widget, register listener for widget submit events through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Productlane account through Composio's Productlane MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Productlane logoProductlane
Api Key

Productlane is a customer support and feedback platform built on Linear. It helps companies collect, organize, and act on customer feedback for better product decisions.

39 Tools

Introduction

This guide walks you through connecting Productlane to Google ADK using the Composio tool router. By the end, you'll have a working Productlane agent that can open productlane widget for user feedback, display specific docs article in widget, register listener for widget submit events through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Productlane account through Composio's Productlane MCP server.

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

Also integrate Productlane with

TL;DR

Here's what you'll learn:
  • Get a Productlane account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Productlane
  • Build an agent that connects to Productlane through MCP
  • Interact with Productlane 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 Productlane MCP server, and what's possible with it?

The Productlane MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Productlane account. It provides structured and secure access to your customer feedback and support workflows, so your agent can programmatically control the Productlane widget, surface documentation, listen for widget events, and manage user interaction—all on your behalf.

  • Dynamic widget control: Let your agent open, close, enable, disable, or toggle the Productlane widget in response to customer or team actions.
  • Contextual docs surfacing: Automatically display specific Productlane documentation articles within the widget to assist users at the right moment.
  • Event-driven automation: Register or remove event listeners so your agent can react to widget events like open, close, submit, or widget load—enabling smart, real-time workflows.
  • Seamless widget experience: Programmatically manage the widget's state across your app to ensure users always get the right support touchpoint.
  • Custom interaction flows: Use the widget's event system to trigger your own logic or follow-ups based on how users interact with Productlane support.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step09 STEPS
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
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio 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.
  • 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.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Productlane via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

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
6

Import modules and validate environment

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.")
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
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["productlane"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
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
8

Set up the McpToolset and create the Agent

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 Productlane operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
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
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

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

Complete Code

Here's the complete code to get you started with Productlane and Google ADK:

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=["productlane"],
)

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 Productlane operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Productlane with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Productlane using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Productlane 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.

TOOLS

Supported Tools

Every Productlane action and event your agent gets out of the box.

Create Changelog Entry

Tool to create a new changelog entry in Productlane.

Create Company

Tool to create a new company in Productlane.

Create Contact

Tool to create a new contact in your Productlane workspace with optional company linking.

Create Feedback

Tool to create new feedback in Productlane.

Create Insight

Tool to create a new insight/thread in Productlane workspace.

Create Thread

Tool to create a new thread in Productlane.

Create Upvote

Tool to create an upvote for a project or issue.

Delete Company

Tool to delete a company by its unique ID.

Delete Contact

Tool to delete a contact by ID.

Delete Upvote

Tool to delete an upvote by its unique ID.

Enable Productlane Widget

Tool to enable the Productlane widget.

Get Changelog

Tool to retrieve a published changelog by ID from Productlane.

Get Company by ID

Tool to retrieve a company by its unique ID.

Get Contact

Tool to retrieve a contact by ID or email from Productlane.

Get Help Center Article

Tool to retrieve a help center article by its ID.

Get Insight

Tool to retrieve an insight/thread by its ID.

Get Issue by ID

Tool to retrieve a specific issue by its ID from a workspace.

Get Linear Customer Options

Tool to retrieve available Linear customer statuses and tiers for your workspace.

Get Project

Tool to retrieve a project by its ID from a workspace.

Get Workspace

Tool to fetch workspace details by ID.

Invite User to Workspace

Tool to invite a new user to your Productlane workspace.

List Changelogs

Tool to list all published changelogs for a workspace by ID.

List Companies

Tool to list all companies in Productlane.

List contacts

Tool to retrieve all contacts for your workspace.

List Help Center Articles

Tool to list all help center articles for a specific workspace.

List Insights

Tool to list all threads/insights for your workspace with optional filtering.

List Productlane Issues

Tool to retrieve all issues from a Productlane workspace.

List Workspace Members

Tool to retrieve all members of your workspace with their roles and user information.

List Projects

Tool to retrieve all projects within a workspace.

Update Company

Tool to update an existing company record in Productlane by its unique identifier.

Update Contact

Tool to update an existing contact in Productlane.

Update Insight

Tool to update an existing insight (thread) by ID.

Close Productlane Widget

Tool to close the Productlane widget.

Disable Productlane Widget

Tool to disable the Productlane widget across the entire page.

Widget off event

Tool to remove a previously registered widget event listener.

Register Widget Event Listener

Tool to register a listener for Productlane widget events.

Open Productlane Widget

Tool to generate a JavaScript snippet that opens the Productlane widget.

Open Productlane Docs Article in Widget

Tool to open a specific docs article in the Productlane widget.

Toggle Productlane Widget

Tool to toggle the Productlane widget between open and closed states.

FAQ

Frequently asked questions

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

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 Productlane tools.

Yes, absolutely. You can configure which Productlane 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.

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 Productlane data and credentials are handled as safely as possible.

Start with Productlane.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Productlane tool your agent needs.Free to start.

Start building