How to integrate Forcemanager MCP with LangChain

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Forcemanager Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting Forcemanager to LangChain using the Composio tool router. By the end, you'll have a working Forcemanager agent that can delete a contact by their id, get details for a specific sales order, retrieve company info using company id, delete a saved view for my team through natural language commands.

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

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

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Forcemanager project to Composio
  • Create a Tool Router MCP session for Forcemanager
  • Initialize an MCP client and retrieve Forcemanager tools
  • Build a LangChain agent that can interact with Forcemanager
  • 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 Forcemanager MCP server, and what's possible with it?

The Forcemanager MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Forcemanager account. It provides structured and secure access to your CRM data, so your agent can perform actions like retrieving activity details, managing companies and contacts, and organizing sales orders on your behalf.

  • Activity management and retrieval: Instantly fetch specific sales activities or remove outdated ones, helping you keep your team's daily records up to date.
  • Company and contact administration: Easily get detailed company or contact information, or delete records when they're no longer needed—all with your agent's help.
  • Sales order and line control: Let your agent delete sales orders or individual order lines, streamlining your sales workflow and keeping data clean.
  • Master data maintenance: Empower your agent to manage master-data values, ensuring your CRM stays accurate and relevant as your business evolves.
  • Saved view organization: Ask your agent to delete saved views you no longer use, keeping your workspace focused and clutter-free.

Supported Tools & Triggers

Tools
Delete ActivityDelete an existing activity by ID.
Delete CompanyTool to delete a company by its ForceManager ID.
Delete ContactDelete an existing contact by ID.
Delete Sales OrderDelete a sales order by ID using ForceManager REST API.
Delete Sales Order LineDelete a sales order line by ID using ForceManager REST API.
Delete Master Data ValueDelete a master-data value (Z_ table) by ID using ForceManager REST API.
Delete ViewDelete a saved view by ID.
Get ActivityTool to get a single activity by ID.
Get CompanyTool to get a single company by ID.
Get Internal IDTool to retrieve ForceManager internal IDs mapping for a given externalId and entity type.
Get ProductTool to get a single product by ID.
Get Sales Order LineTool to get a single sales order line by ID.
Get UserTool to get a single user by ID.
Get ViewTool to get a single view by ID.
List ViewsTool to list saved view filters.
Update ActivityTool to update an existing activity by ID.
Update CompanyUpdate Company
Update ProductTool to update a product by ID in ForceManager.
Update Sales OrderUpdate Sales Order
Update Sales Order LineTool to update sales order line by ID.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

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

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.

Install dependencies

pip install composio-langchain langchain-mcp-adapters langchain python-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 is the core agent framework
  • python-dotenv loads environment variables

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

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

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

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
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 Forcemanager tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Forcemanager
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['forcemanager']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Forcemanager 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 Forcemanager tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "forcemanager-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

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

Set up interactive chat interface

conversation_history = []

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

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts 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 ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

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

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['forcemanager']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "forcemanager-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Forcemanager related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've successfully built a LangChain agent that can interact with Forcemanager 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.

How to build Forcemanager MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Forcemanager MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Forcemanager MCP with Claude Agent SDK

Google ADK

Google ADK

Use Forcemanager MCP with Google ADK

Vercel AI SDK

Vercel AI SDK

Use Forcemanager MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Forcemanager MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Forcemanager MCP with LlamaIndex

CrewAI

CrewAI

Use Forcemanager MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Forcemanager MCP?

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

Can I use Tool Router MCP with LangChain?

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free