# How to integrate Parma MCP with CrewAI

```json
{
  "title": "How to integrate Parma MCP with CrewAI",
  "toolkit": "Parma",
  "toolkit_slug": "parma",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/parma/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/parma/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:21:19.883Z"
}
```

## Introduction

This guide walks you through connecting Parma to CrewAI using the Composio tool router. By the end, you'll have a working Parma agent that can show your parma crm user profile details, list all dataset ids in parma ckan, fetch full metadata for all parma datasets through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Parma account through Composio's Parma MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Parma with

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

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Parma connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Parma
- Build a conversational loop where your agent can execute Parma 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 Parma MCP server, and what's possible with it?

The Parma MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, and more directly to your Parma CRM account. It provides structured and secure access to your CRM data, so your agent can retrieve user profiles, access dataset catalogs, and manage critical business information on your behalf.
- Comprehensive dataset catalog access: Instantly retrieve dcat-us 1.1 compliant metadata for all datasets in your Parma open data portal, making it easy to audit or analyze your entire data catalog.
- Personalized user profile retrieval: Ask your agent to fetch the authenticated user's profile details, helping you quickly access account info or tailor interactions for specific users.
- Efficient dataset identification: Let your agent list all dataset identifiers from Parma's CKAN instance, streamlining workflows that depend on knowing what's available in your data ecosystem.
- Data-driven relationship management: Empower your agent to surface, summarize, or cross-reference CRM datasets, deepening insights into your business relationships and opportunities.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PARMA_ADD_RELATIONSHIP_TO_GROUP` | Add Relationship to Group | Tool to add a relationship to a group in Parma. Use when you need to associate an existing relationship with a group. |
| `PARMA_CREATE_NOTE` | Create Note | Tool to create a new note in the Parma account. Use when you need to add a note linked to specific relationships. |
| `PARMA_CREATE_RELATIONSHIP` | Create Relationship | Tool to create a new relationship in Parma. Use when you need to add a new person or company to your Parma account. |
| `PARMA_DATA_JSON` | Get data.json metadata | Tool to retrieve DCAT-US 1.1 compliant metadata of all datasets. Use when you need the complete catalog JSON (data.json) from Parma’s open data portal. |
| `PARMA_DELETE_RELATIONSHIP` | Delete Relationship | Tool to delete a relationship from Parma by its ID. Use when you need to remove an existing relationship between entities. Returns success confirmation after deletion (HTTP 204). |
| `PARMA_GET_PIPELINE` | Get Pipeline | Tool to retrieve a pipeline by its ID. Use when you need to fetch details about a specific pipeline. |
| `PARMA_GET_RELATIONSHIP` | Get Relationship | Tool to retrieve a relationship by its unique ID. Use when you need to get detailed information about a specific relationship. |
| `PARMA_GET_STAGE` | Get Stage | Tool to retrieve a stage by its unique identifier. Use when you need to fetch details about a specific stage in a pipeline. |
| `PARMA_GET_USER` | Get User by ID | Tool to retrieve a user by their unique ID. Use when you need to fetch details for a specific user. |
| `PARMA_GET_USER_PROFILE` | Get User Profile | Tool to retrieve the authenticated user's profile. Use after obtaining a valid auth token to fetch current user account details. |
| `PARMA_LIST_DEALS` | List Deals | Tool to retrieve all deals from the Parma account. Use when you need to list deals, filter by pagination, or get an overview of all deals in the system. |
| `PARMA_LIST_GROUPS` | List Groups | Tool to retrieve all groups in the Parma account. Use when you need to list groups, optionally filtered by a search query. |
| `PARMA_LIST_NOTES` | List Notes | Tool to retrieve all notes from the Parma account. Use when you need to list or search through notes associated with relationships. |
| `PARMA_LIST_PIPELINES` | List Pipelines | Tool to list all pipelines in the Parma account. Use when you need to retrieve available pipelines and their details. |
| `PARMA_LIST_RELATIONSHIP_GROUPS` | List Relationship Groups | Tool to retrieve all groups linked to a specific relationship. Use when you need to see which groups are associated with a given relationship ID. |
| `PARMA_LIST_RELATIONSHIP_NOTES` | List Relationship Notes | Tool to list all notes linked to a relationship. Use when you need to retrieve all notes associated with a specific relationship ID. |
| `PARMA_LIST_RELATIONSHIPS` | List Relationships | Tool to list all relationships in the Parma account. Use when you need to retrieve and filter relationships by various criteria such as name, type, or contact details. |
| `PARMA_LIST_STAGES` | List Stages | Tool to retrieve all stages in the Parma account. Use when you need to list pipeline stages or check available stage configurations. |
| `PARMA_LIST_USERS` | List Users | Tool to list all users in the Parma account. Use when you need to retrieve the complete list of users with their IDs, names, and email addresses. |
| `PARMA_PACKAGE_LIST` | List Parma CKAN datasets | Tool to retrieve all dataset identifiers from the Parma CKAN instance. Use when you need to list every available dataset ID. |
| `PARMA_REMOVE_RELATIONSHIP_FROM_GROUP` | Remove Relationship From Group | Tool to remove a relationship from a group. Use when you need to dissociate a relationship from a specific relationship group. Returns success status on completion (HTTP 204). |
| `PARMA_UPDATE_NOTE` | Update Note | Tool to update an existing note in the Parma account. Use when you need to modify the content, datetime, or relationships of a specific note. |
| `PARMA_UPDATE_RELATIONSHIP` | Update Relationship | Tool to update an existing relationship in the Parma account. Use when you need to modify relationship details such as name, description, type, or associated groups. |

## Supported Triggers

None listed.

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

The Parma MCP server is an implementation of the Model Context Protocol that connects your AI agent to Parma. It provides structured and secure access so your agent can perform Parma 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 Parma 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 Parma 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 Parma 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 Parma

**What's happening:**
- You create a Parma only session through Composio
- Composio returns an MCP HTTP URL that exposes Parma tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["parma"])

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=["parma"],
)
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 Parma through Composio's Tool Router. The agent can perform Parma 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 Parma MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/parma/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/parma/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/parma/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/parma/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/parma/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/parma/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/parma/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/parma/framework/cli)
- [Google ADK](https://composio.dev/toolkits/parma/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/parma/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/parma/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/parma/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/parma/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.
- [Affinity](https://composio.dev/toolkits/affinity) - 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.
- [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.

## Frequently Asked Questions

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

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

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

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

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