How to integrate CompanyCam MCP with LangChain

This guide walks you through connecting CompanyCam to LangChain using the Composio tool router. By the end, you'll have a working CompanyCam agent that can create your projects, add project photos, tag your photos, create project tasks, and add comments through natural language commands. This guide will help you understand how to give your LangChain agent real control over a CompanyCam account through Composio's CompanyCam MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

CompanyCam logoCompanyCam
Api Key

CompanyCam is a photo-first jobsite management platform for project teams. It helps crews document work, coordinate jobs, and share visual updates fast.

24 Tools

Introduction

This guide walks you through connecting CompanyCam to LangChain using the Composio tool router. By the end, you'll have a working CompanyCam agent that can create your projects, add project photos, tag your photos, create project tasks, and add comments through natural language commands.

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

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

Also integrate CompanyCam with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your CompanyCam project to Composio
  • Create a Tool Router MCP session for CompanyCam
  • Initialize an MCP client and retrieve CompanyCam tools
  • Build a LangChain agent that can interact with CompanyCam
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the CompanyCam MCP server, and what's possible with it?

The CompanyCam MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your CompanyCam account. It provides structured and secure access to your projects, customers, jobsite photos, tasks, comments, labels, tags, and users, so your agent can create projects, document jobsites, coordinate tasks, organize photos, and share project updates on your behalf.

  • Project and customer management: Have your agent create, search, review, and update projects and customer records, including addresses, contact details, and notes.
  • Jobsite photo documentation: Direct your agent to add photos from public web links, review project photos, update photo descriptions, and organize images with tags.
  • Task coordination: Let the agent create, review, and update project tasks, track completion status, and assign available team members.
  • Project communication: Instruct your agent to add comments to projects or photos and review existing discussions before sharing an update.
  • Project organization: Have your agent apply project labels, create reusable photo tags, and find projects using lifecycle, assignee, or text-based searches.

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

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
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

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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 your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with CompanyCam functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to CompanyCam tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['companycam']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to CompanyCam tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use CompanyCam tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "companycam-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our CompanyCam MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available CompanyCam tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any CompanyCam related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with CompanyCam and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['companycam']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "companycam-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any CompanyCam related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with CompanyCam through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Add Comment

Add a comment to either a CompanyCam project or photo.

Add Photo Tags

Attach media tags by display name.

Add Project Labels

Attach project labels by display name.

Add Project Photo From URL

Add a photo to a CompanyCam project by having CompanyCam fetch a publicly reachable HTTPS image URL.

Create Customer

Create a CompanyCam customer with optional contact details, company status, notes, address, and initial contacts.

Create Project

Create a CompanyCam project with its required address and optional contact, customer, location, and template details.

Create Project Task

Create a task on a CompanyCam project with task details and optional assignees.

Create Photo Tag

Create a reusable CompanyCam media tag for organizing photos.

Get Account Context

Return the connected CompanyCam user and company so an agent can identify the account, role, and company before acting.

Get Photo

Get one CompanyCam photo by ID.

Get Project

Get one CompanyCam project by ID.

List Comments

List comments attached to either a CompanyCam project or photo.

List Customers

List or search CompanyCam customers by name or contact text.

List Project Labels

List reusable CompanyCam project labels that can be attached to projects.

List Project Photos

List and filter photos in a CompanyCam project by tags, users, or groups, one cursor page at a time.

List Projects

List projects with optional lifecycle and assigned-user filters, one cursor page at a time.

List Project Tasks

List tasks for a CompanyCam project, including status, completion, assignees, and attached media.

List Photo Tags

List reusable CompanyCam media tags and return an opaque cursor for the next page.

List Users

List CompanyCam users available for task assignment and project workflows.

Search Projects

Search CompanyCam projects by a free-text query when project list filters are insufficient.

Set Photo Description

Create or replace the description attached to a CompanyCam photo.

Update Customer

Update the name, notes, city, or postal code of an existing CompanyCam customer.

Update Project

Update editable project identity, address, or primary-contact fields without changing archive state.

Update Project Task

Update a CompanyCam project task's details or add and retain assignees.

FAQ

Frequently asked questions

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

Yes, you can. LangChain 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 CompanyCam tools.

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

Start with CompanyCam.It takes 30 seconds.

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

Start building