# How to integrate Affinity MCP with CrewAI ```json { "title": "How to integrate Affinity MCP with CrewAI", "toolkit": "Affinity", "toolkit_slug": "affinity", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/affinity/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/affinity/framework/crew-ai.md", "updated_at": "2026-05-12T10:00:19.548Z" } ``` ## Introduction This guide walks you through connecting Affinity to CrewAI 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 CrewAI 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/affinity/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/affinity/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/affinity/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/affinity/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/affinity/framework/codex) - [OpenClaw](https://composio.dev/toolkits/affinity/framework/openclaw) - [Hermes](https://composio.dev/toolkits/affinity/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/affinity/framework/cli) - [Google ADK](https://composio.dev/toolkits/affinity/framework/google-adk) - [LangChain](https://composio.dev/toolkits/affinity/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/affinity/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/affinity/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/affinity/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Affinity connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Affinity - Build a conversational loop where your agent can execute Affinity operations ## What is CrewAI? CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews. Key features include: - Agent Roles: Define specialized agents with specific goals and backstories - Task Management: Create tasks with clear descriptions and expected outputs - Crew Orchestration: Combine agents and tasks into collaborative workflows - MCP Integration: Connect to external tools through Model Context Protocol ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `AFFINITY_GET_A_COMPANY_S_LIST_ENTRIES` | Get a company s list entries | Summarize company data across all lists, including list-specific fields and metadata like creation date and author. Access requires "Export data from Lists" permission. | | `AFFINITY_GET_A_COMPANY_S_LISTS` | Get a company s lists | Returns metadata for all the Lists on which the given Company appears. | | `AFFINITY_GET_ALL_COMPANIES` | Get all companies | Affinity API allows paginated access to company info and custom fields. Use `fieldIds` or `fieldTypes` to specify data in a request. Retrieve field IDs/Types via GET `/v2/companies/fields`. Export permission needed. | | `AFFINITY_GET_ALL_LIST_ENTRIES_ON_A_LIST` | 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`. "Export data from Lists" permission is necessary. | | `AFFINITY_GET_ALL_LIST_ENTRIES_ON_A_SAVED_VIEW` | 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. It doesn't maintain sort order, supports only sheet-type views, and requires export permissions. | | `AFFINITY_GET_ALL_OPPORTUNITIES` | Get all opportunities | Pagination through Opportunities in Affinity yields basic info but excludes field data. For field data, use specified GET endpoints. "Export data from Lists" permission needed. | | `AFFINITY_GET_ALL_PERSONS` | Get all persons | The Affinity API offers paginated access to Person data using `fieldIds` or `fieldTypes`. Bulk extraction needs special permissions and supports multiple parameters. | | `AFFINITY_GET_A_PERSON_S_LIST_ENTRIES` | 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. Requires "Export data from Lists" permission. | | `AFFINITY_GET_A_PERSON_S_LISTS` | Get a person s lists | Returns metadata for all the Lists on which the given Person appears. | | `AFFINITY_GET_A_SINGLE_COMPANY` | Get a single company | Retrieve basic company info and specific field data by using `fieldIds` or `fieldTypes` parameters. Multiple fields can be queried. No field data if parameters aren't specified. Requires "Export All Organizations directory" permission. | | `AFFINITY_GET_A_SINGLE_OPPORTUNITY` | Get a single opportunity | Get basic details about an Opportunity without field data via provided endpoints. Field data requires using specific list entry APIs and the "Export data from Lists" permission. | | `AFFINITY_GET_A_SINGLE_PERSON` | Get a single person | Use GET `/v2/persons/fields` with `fieldIds` or `fieldTypes` for detailed data; basic info by default. Request multiple fields at once. "Export All People" permission needed. | | `AFFINITY_GET_CURRENT_USER` | Get current user | Returns metadata about the current user. | | `AFFINITY_GET_METADATA_ON_ALL_LISTS` | Get metadata on all lists | Returns metadata on Lists. | | `AFFINITY_GET_METADATA_ON_A_SINGLE_LIST` | Get metadata on a single list | Returns metadata on a single List. | | `AFFINITY_GET_METADATA_ON_A_SINGLE_LIST_S_FIELDS` | Get metadata on a single list s fields | Returns metadata on the Fields available on a single List. Use the returned Field IDs to request field data from the GET `/v2/lists/{listId}/list-entries` endpoint. | | `AFFINITY_GET_METADATA_ON_A_SINGLE_SAVED_VIEW` | Get metadata on a single saved view | Returns metadata on a single Saved View. | | `AFFINITY_GET_METADATA_ON_COMPANY_FIELDS` | Get metadata on company fields | Returns metadata on non-list-specific Company Fields. Use the returned Field IDs to request field data from the GET `/v2/companies` and GET `/v2/companies/{id}` endpoints. | | `AFFINITY_GET_METADATA_ON_PERSON_FIELDS` | Get metadata on person fields | Returns metadata on non-list-specific Person Fields. Use the returned Field IDs to request field data from the GET `/v2/persons` and GET `/v2/persons/{id}` endpoints. | | `AFFINITY_GET_METADATA_ON_SAVED_VIEWS` | Get metadata on saved views | Returns metadata on the Saved Views on a List. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Affinity MCP server is an implementation of the Model Context Protocol that connects your AI agent to Affinity. It provides structured and secure access so your agent can perform Affinity 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: - Python 3.9 or higher - A Composio account and API key - A Affinity connection authorized in Composio - An OpenAI API key for the CrewAI LLM - Basic familiarity with Python ### 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 **What's happening:** - composio connects your agent to Affinity via MCP - crewai provides Agent, Task, Crew, and LLM primitives - crewai-tools[mcp] includes MCP helpers - python-dotenv loads environment variables from .env ```bash pip install composio crewai crewai-tools[mcp] python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID scopes the session to your account - OPENAI_API_KEY lets CrewAI use your chosen OpenAI model ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies **What's happening:** - CrewAI classes define agents and tasks, and run the workflow - MCPServerHTTP connects the agent to an MCP endpoint - Composio will give you a short lived Affinity MCP URL ```python import os from composio import Composio from crewai import Agent, Task, Crew from crewai_tools import MCPServerAdapter import dotenv dotenv.load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") ``` ### 5. Create a Composio Tool Router session for Affinity **What's happening:** - You create a Affinity only session through Composio - Composio returns an MCP HTTP URL that exposes Affinity tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["affinity"]) url = session.mcp.url ``` ### 6. Initialize the MCP Server **What's Happening:** - Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication. - MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format. - Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools. - Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops. - Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries. ```python server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users search the internet effectively", backstory="You are a helpful assistant with access to search tools.", tools=tools, verbose=False, max_iter=10, ) ``` ### 7. Create a CLI Chatloop and define the Crew **What's Happening:** - Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable. - Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean. - Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses. - Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context. - Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response. - Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity. ```python print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Complete Code ```python from crewai import Agent, Task, Crew, LLM from crewai_tools import MCPServerAdapter from composio import Composio from dotenv import load_dotenv import os load_dotenv() 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.") # Initialize Composio and create a session composio = Composio(api_key=COMPOSIO_API_KEY) session = composio.create( user_id=COMPOSIO_USER_ID, toolkits=["affinity"], ) url = session.mcp.url # Configure LLM llm = LLM( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY"), ) server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users with internet searches", backstory="You are an expert assistant with access to Composio Search tools.", tools=tools, llm=llm, verbose=False, max_iter=10, ) print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Conclusion You now have a CrewAI agent connected to Affinity through Composio's Tool Router. The agent can perform Affinity operations through natural language commands. Next steps: - Add role-specific instructions to customize agent behavior - Plug in more toolkits for multi-app workflows - Chain tasks for complex multi-step operations ## How to build Affinity MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/affinity/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/affinity/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/affinity/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/affinity/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/affinity/framework/codex) - [OpenClaw](https://composio.dev/toolkits/affinity/framework/openclaw) - [Hermes](https://composio.dev/toolkits/affinity/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/affinity/framework/cli) - [Google ADK](https://composio.dev/toolkits/affinity/framework/google-adk) - [LangChain](https://composio.dev/toolkits/affinity/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/affinity/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/affinity/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/affinity/framework/llama-index) ## Related Toolkits - [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place. - [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up. - [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships. - [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place. - [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently. - [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing. - [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. - [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place. - [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources. - [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations. - [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface. - [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently. - [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools. - [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data. - [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place. - [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process. - [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools. - [Firmao](https://composio.dev/toolkits/firmao) - Firmao is a business information platform offering company, industry, and market data. Use it to quickly research firms and gain competitive market insights. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Affinity MCP? 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. ### Can I use Tool Router MCP with CrewAI? Yes, you can. CrewAI 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. ### Can I manage the permissions and scopes for Affinity while using Tool Router? 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. ### 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 Affinity data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)