How to integrate Bitbucket MCP with CrewAI

This guide walks you through connecting Bitbucket to CrewAI using the Composio tool router. By the end, you'll have a working Bitbucket agent that can create a new branch off main, open a pull request for your feature, comment on the latest open issue through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Bitbucket account through Composio's Bitbucket MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Bitbucket logoBitbucket
Oauth2

Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.

105 Tools

Introduction

This guide walks you through connecting Bitbucket to CrewAI using the Composio tool router. By the end, you'll have a working Bitbucket agent that can create a new branch off main, open a pull request for your feature, comment on the latest open issue through natural language commands.

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

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

Also integrate Bitbucket with

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

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

The Bitbucket MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bitbucket account. It provides structured and secure access to your repositories, issues, and pull requests, so your agent can create branches, manage issues, review code, and handle repository operations for you.

  • Branch and repository management: Let your agent create new branches for feature work or initialize fresh repositories within your Bitbucket workspace—no manual setup required.
  • Automated issue tracking: Have your agent create, comment on, or delete issues to streamline team collaboration and bug tracking directly from your workflows.
  • Pull request automation: Empower your agent to open new pull requests for code review, ensuring changes are properly tracked and integrated.
  • File and snippet operations: Ask your agent to fetch specific files from any branch or commit, or to post comments on code snippets for contextual discussions.
  • User profile and workspace insights: Retrieve your Bitbucket user profile details on demand, making it easy to personalize and audit agent-driven actions.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Bitbucket connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Bitbucket via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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
5

Import dependencies

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")
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 Bitbucket MCP URL
6

Create a Composio Tool Router session for Bitbucket

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["bitbucket"])

url = session.mcp.url
What's happening:
  • You create a Bitbucket only session through Composio
  • Composio returns an MCP HTTP URL that exposes Bitbucket tools
7

Initialize the MCP Server

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,
    )
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.
8

Create a CLI Chatloop and define the Crew

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

Complete Code

Here's the complete code to get you started with Bitbucket and CrewAI:

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=["bitbucket"],
)
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 Bitbucket through Composio's Tool Router. The agent can perform Bitbucket 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
TOOLS

Supported Tools

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

Approve Pull Request

Tool to approve a pull request as the authenticated user.

Browse repository path

Tool to retrieve content for a file path or browse directory contents at a specified revision in a Bitbucket repository.

Create a branch

Creates a new branch in a Bitbucket repository from a target commit hash; the branch name must be unique, adhere to Bitbucket's naming conventions, and not include the 'refs/heads/' prefix.

Create an issue

Creates a new issue in a Bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component IDs exist.

Create an issue comment

Adds a new comment with markdown support to an existing Bitbucket issue.

Create a pull request

Creates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.

Create pull request comment

Creates a new comment on a Bitbucket pull request.

Create commit report annotations

Adds multiple annotations to a commit report in bulk.

List commits from revision (POST)

Tool to list commits from a revision using POST method.

Create repository

Creates a new Bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project_key` is not provided.

Create snippet comment

Posts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet.

Create team pipeline variable

Creates a team-level pipeline configuration variable in Bitbucket.

Create user pipeline variable

Creates a user-level pipeline variable for Bitbucket pipelines.

Delete commit comment

Permanently deletes a specific comment on a commit.

Delete issue

Permanently deletes a specific issue, identified by its `issue_id`, from the repository specified by `repo_slug` within the given `workspace`.

Delete pull request comment

Permanently deletes a specific pull request comment (top-level, inline, or threaded reply).

Delete commit report annotation

Deletes a single annotation matching the provided ID from a commit report.

Delete repository

Permanently deletes a specified Bitbucket repository; this action is irreversible and does not affect forks.

Delete snippet watch

Stops watching a specific snippet.

Delete user pipeline variable

Permanently deletes a user-level pipeline configuration variable identified by its UUID.

Get branch

Retrieves detailed information about a specific branch in a Bitbucket repository.

Get Commit Build Status

Get a specific build status for a commit in Bitbucket.

Get Commit Changes

Tool to retrieve a page of changes made in a specified commit, showing all changed files with their change statistics (lines added/removed, status).

Get commit comment

Retrieves a specific comment from a commit by its ID.

Get Commit Diff

Tool to retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket repository.

Get current user (v2)

Tool to retrieve complete profile information for the currently authenticated Bitbucket user.

Get deployment environment variables

Retrieves deployment environment level variables for a specific Bitbucket repository environment.

Get file from repository

Retrieves a specific file's content from a Bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.

Get hook events

Retrieves a paginated list of all valid webhook events for a specified entity type (repository or workspace).

Get OpenID configuration for OIDC in Pipelines

Retrieves the OpenID Connect discovery configuration for Bitbucket Pipelines OIDC.

Get Pull Request

Get a single pull request by ID with complete details.

Get pull request comment

Tool to retrieve a specific comment from a pull request by its ID.

Get Pull Request Commits

Tool to retrieve commits for a specified pull request.

Get Pull Request Diff

Tool to fetch the unified diff for a Bitbucket pull request (follows 302 redirect to repository diff).

Get Pull Request Diffstat

Tool to get the diffstat for a Bitbucket pull request, showing all changed files with their change statistics (lines added/removed, status).

Get Repository Branching Model

Return the branching model as applied to the repository.

Get Repository Commit

Tool to retrieve detailed information about a specific commit in a Bitbucket repository.

Get commit comments

Retrieves all comments on a specific commit in a Bitbucket repository.

Get commit report

Returns a single report matching the provided ID from a commit.

Get Commit Reports

Tool to get reports linked to a specific commit.

Get commit report annotation

Returns a single annotation matching the provided ID from a commit report.

Get commit statuses

Returns all build statuses (e.

Get effective branching model

Retrieves the effective branching model for a Bitbucket repository, showing which branching model is currently applied (including any inheritance from project-level settings).

Get Repository Environment

Retrieve detailed information about a specific deployment environment in a Bitbucket repository.

Get file commit history

Returns a paginated list of commits that modified the specified file.

Check if user voted for issue

Tool to check whether the authenticated user has voted for a specific issue in a Bitbucket repository.

Get Repositories Merge Base

Get the merge base (best common ancestor) between two commits in a Bitbucket repository.

Get specific pipeline

Retrieve a specified pipeline from a Bitbucket repository.

Get repository pipelines caches

Retrieves the repository pipelines caches.

Get repository pipeline runners

Retrieves the list of self-hosted runners configured for a repository's pipelines.

Get repository pipeline schedules

Retrieves configured pipeline schedules for a Bitbucket repository.

Get repository SSH known hosts

Retrieves repository-level SSH known hosts configured for Bitbucket Pipelines.

Get repository pipeline variables

Retrieves repository-level pipeline variables for a specific Bitbucket repository.

Get pipeline steps

Retrieves all steps for a given pipeline.

Get pull requests activity log

Get paginated activity log for all pull requests in a repository.

Get pull request comments

Retrieves a paginated list of comments on a specific pull request in a Bitbucket repository.

Get pull request statuses

Returns all build statuses (e.

Get repository refs

Returns the branches and tags in the repository.

Get tag

Retrieves detailed information about a specific tag in a Bitbucket repository.

Get repositories src

Lists the contents of the root directory on the repository's main branch without needing to specify a commit or branch.

Get repository watchers

Retrieves a paginated list of all the watchers on the specified repository.

Get repository

Retrieves detailed information about a specific repository in a Bitbucket workspace.

Get Repository Patch

Tool to retrieve the git patch content for a Bitbucket repository at a specified revision or commit range.

Get snippet

Retrieves a specific Bitbucket snippet by its encoded ID from an existing workspace, returning its metadata and file structure.

Get snippet watch status

Checks if the current user is watching a specific snippet.

Get SSH keys for user

Retrieves a paginated list of SSH keys for a specified Bitbucket user.

Get user

Retrieves public profile information for a specific Bitbucket user by username or UUID.

Get user emails

Returns all the authenticated user's email addresses, both confirmed and unconfirmed.

Get user email details

Retrieves details about a specific email address for the authenticated user.

Get user permissions for repositories

Returns an object for each repository the caller has explicit access to, including their permission level.

Get user permissions for workspaces

Retrieves workspace memberships and permission levels for the authenticated user.

Get user workspaces

Tool to retrieve all workspaces accessible to the authenticated user.

Get workspace

Retrieves detailed information about a specific Bitbucket workspace.

Get Workspace Pull Requests by User

Tool to get all workspace pull requests authored by a specified user.

Search code in workspace

Tool to search for code in the repositories of the specified workspace.

List branches

Lists branches in a Bitbucket repository with optional server-side filtering by name pattern (BBQL) and sorting.

List commits

Tool to retrieve a page of commits from a Bitbucket repository.

List commits from revision

Tool to list commits starting from a specific revision in a Bitbucket repository.

List commits on master

Lists commits on the master branch of a Bitbucket repository.

List deployments

Lists deployments for a specified Bitbucket repository.

List issues in a repository

Lists issues in a Bitbucket repository with optional filtering by state, priority, kind, or assignee.

List pipelines

Tool to find pipelines in a Bitbucket repository.

List pull requests

Lists pull requests in a specified, accessible Bitbucket repository, optionally filtering by state (OPEN, MERGED, DECLINED).

List pull request tasks

Lists all tasks associated with a pull request in a Bitbucket repository.

List all public repositories

Retrieves a paginated list of all public repositories on Bitbucket.

List repository environments

List all deployment environments configured for a Bitbucket repository.

List repositories in workspace

Lists repositories in a specified Bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results.

List repository paths

Lists file and directory entries under a repository path at a given revision, with optional breadth-first recursion via max_depth for repository traversal and scanning.

List snippets

Returns all snippets accessible to the authenticated user.

List tags

Lists tags in a Bitbucket repository with optional server-side filtering by name pattern or commit hash (BBQL) and sorting.

List versions

Lists versions (milestones) in a Bitbucket repository's issue tracker.

List workspace members

Lists all members of a specified Bitbucket workspace; the workspace must exist.

List workspace projects

Lists projects in a specified Bitbucket workspace.

List workspaces

Lists Bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted.

Merge Pull Request

Tool to merge a Bitbucket Cloud pull request via the REST API.

Request Pull Request Changes

Tool to request changes on a pull request as the authenticated user.

Resolve pull request comment

Tool to resolve or reopen a pull request comment thread.

Search code in user repositories

Tool to search for code in the repositories of a specified user.

Update commit insight report

Create or update an insight report for a commit.

Update an issue

Updates an existing issue in a Bitbucket repository by modifying specified attributes; requires `workspace`, `repo_slug`, `issue_id`, and at least one attribute to update.

Update Pull Request

Tool to update an existing pull request's editable fields (e.

Update commit comment

Updates the contents of a comment on a commit.

Update commit report annotation

Creates or updates an individual annotation for a commit report.

Update team pipeline variable

Updates a team-level pipeline configuration variable in Bitbucket.

Update user pipeline variable

Updates a user-level pipeline variable for Bitbucket pipelines.

FRAMEWORKS

How to build Bitbucket MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Bitbucket MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Bitbucket MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Bitbucket MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Bitbucket MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Bitbucket MCP with Claude Cowork

Codex logo

Codex

Use Bitbucket MCP with Codex

Cursor logo

Cursor

Use Bitbucket MCP with Cursor

OpenClaw logo

OpenClaw

Use Bitbucket MCP with OpenClaw

Hermes logo

Hermes

Use Bitbucket MCP with Hermes

CLI logo

CLI

Use Bitbucket MCP with CLI

Google ADK logo

Google ADK

Use Bitbucket MCP with Google ADK

LangChain logo

LangChain

Use Bitbucket MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Bitbucket MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Bitbucket MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Bitbucket MCP with LlamaIndex

OpenCode logo

OpenCode

Use Bitbucket MCP with OpenCode

VS Code logo

VS Code

Use Bitbucket MCP with VS Code

FAQ

Frequently asked questions

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

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

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

Start with Bitbucket.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies