How to integrate Affinity MCP with Google ADK

This guide walks you through connecting Affinity to Google ADK using the Composio tool router. By the end, you'll have a working Affinity agent that can list all companies added this week, show all opportunities in active pipeline, get recent contacts linked to acme corp through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Affinity account through Composio's Affinity MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Affinity logoAffinity
Api Key

Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities.

20 Tools

Introduction

This guide walks you through connecting Affinity to Google ADK using the Composio tool router. By the end, you'll have a working Affinity agent that can list all companies added this week, show all opportunities in active pipeline, get recent contacts linked to acme corp through natural language commands.

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

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

Also integrate Affinity with

TL;DR

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

The Affinity MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Affinity account. It provides structured and secure access to your deal, company, and contact data, so your agent can analyze lists, fetch opportunity details, extract company insights, and organize people or organizations on your behalf.

  • Company data extraction and analysis: Let your agent retrieve detailed company profiles, summarize list entries, and pull custom field data for deeper insights and reporting.
  • Opportunity pipeline management: Automatically fetch and review all ongoing opportunities, track changes, and surface high-priority deals for follow-up.
  • List and view organization: Ask your agent to access entries across lists or saved views, aggregating metadata and field values for efficient CRM workflows.
  • Contact and relationship intelligence: Effortlessly browse, analyze, and summarize person records, including their list memberships, activity, and custom fields.
  • Automated CRM reporting: Generate summaries, export data, and monitor changes across companies, people, and opportunities to keep your pipeline up-to-date and actionable.

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

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

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

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Affinity 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 Affinity action and event your agent gets out of the box.

Get a company s list entries

Summarize company data across all lists, including list-specific fields and metadata like creation date and author.

Get a company s lists

Returns metadata for all the Lists on which the given Company appears.

Get all companies

Affinity API allows paginated access to company info and custom fields.

Get all list entries on a list

Access and export essential data and metadata for Companies, Persons, or Opportunities from a List, specifying data via `fieldIds` or `fieldTypes`.

Get all list entries on a saved view

Use the endpoint to access rows in a Saved View with specific filters and selected fields from a web app.

Get all opportunities

Pagination through Opportunities in Affinity yields basic info but excludes field data.

Get all persons

The Affinity API offers paginated access to Person data using `fieldIds` or `fieldTypes`.

Get a person s list entries

Summary: Browse rows for a Person in all Lists, showing field data and entry metadata like creation time and author.

Get a person s lists

Returns metadata for all the Lists on which the given Person appears.

Get a single company

Retrieve basic company info and specific field data by using `fieldIds` or `fieldTypes` parameters.

Get a single opportunity

Get basic details about an Opportunity without field data via provided endpoints.

Get a single person

Use GET `/v2/persons/fields` with `fieldIds` or `fieldTypes` for detailed data; basic info by default.

Get current user

Returns metadata about the current user.

Get metadata on all lists

Returns metadata on Lists.

Get metadata on a single list

Returns metadata on a single List.

Get metadata on a single list s fields

Returns metadata on the Fields available on a single List.

Get metadata on a single saved view

Returns metadata on a single Saved View.

Get metadata on company fields

Returns metadata on non-list-specific Company Fields.

Get metadata on person fields

Returns metadata on non-list-specific Person Fields.

Get metadata on saved views

Returns metadata on the Saved Views on a List.

FAQ

Frequently asked questions

With a standalone Affinity MCP server, the agents and LLMs can only access a fixed set of Affinity tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Affinity 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 Affinity tools.

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

Start with Affinity.It takes 30 seconds.

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

Start building