How to integrate Formdesk MCP with LangChain

Framework Integration Gradient
Formdesk Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting Formdesk to LangChain using the Composio tool router. By the end, you'll have a working Formdesk agent that can add a new field to my registration form, submit a new entry to feedback form 12345, delete the email field from survey form 67890, get details of entry id 555 in form 4321 through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Formdesk account through Composio's Formdesk 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 Formdesk project to Composio
  • Create a Tool Router MCP session for Formdesk
  • Initialize an MCP client and retrieve Formdesk tools
  • Build a LangChain agent that can interact with Formdesk
  • 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 Formdesk MCP server, and what's possible with it?

The Formdesk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Formdesk account. It provides structured and secure access to your online forms, so your agent can perform actions like submitting entries, managing form fields, handling visitors, and retrieving detailed information on your behalf.

  • Automated form entry submission: Let your agent instantly submit new responses to any of your Formdesk forms using collected or generated data.
  • Dynamic form structure management: Easily create new fields or delete existing ones, allowing your agent to adapt forms as your requirements change.
  • Detailed entry and field retrieval: Have your agent fetch comprehensive details about specific form entries or fields for auditing, review, or analysis.
  • Visitor management automation: Add or remove visitors in your forms, streamlining registration and access workflows with AI assistance.
  • Effortless form and data cleanup: Direct your agent to delete forms, entries, fields, or visitors, keeping your Formdesk workspace organized and up to date.

Supported Tools & Triggers

Tools
Automatic LoginTool to perform automatic login to Formdesk and retrieve an access token.
Create Formdesk EntryTool to submit a new entry to a Formdesk form.
Create FieldTool to create a new field in a specific Formdesk form.
Create VisitorTool to add a new visitor to a specific Formdesk form.
Delete Formdesk EntryTool to delete a specific entry from a Formdesk form.
Delete Field in FormdeskTool to delete a specific field in a Formdesk form.
Delete Form in FormdeskTool to delete a specific form.
Delete Visitor in FormdeskTool to delete a specific visitor in a Formdesk form.
Get Entry DetailsTool to retrieve detailed information about a specific Formdesk entry.
Get Field DetailsTool to retrieve detailed information about a specific field.
Get Form DetailsTool to retrieve detailed information about a specific Formdesk form.
Get Form EntriesTool to retrieve all entries for a specified Formdesk form.
Get Form FieldsTool to retrieve all fields of a specific form.
Get Form ListTool to retrieve a list of all forms available in the account.
Get Form VisitorsTool to retrieve all visitors for a specified Formdesk form.
Get Visitor DetailsTool to retrieve detailed information about a specific Formdesk visitor.
KVK Handelsregister LookupTool to lookup company details from the Dutch KVK Handelsregister.
Manage Visitor EntriesTool to list or retrieve a visitor's own form entries.
Create Multi-Page FormTool to create a multi-page Formdesk form.
Prepopulate Formdesk FieldsTool to prepopulate form fields.
Update FieldTool to update an existing field definition on a Formdesk form.
Update FormTool to update an existing form.
Update VisitorTool to update an existing visitor for a given form.
Webhook IntegrationTool to send form submission data to external webhooks.

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 Formdesk 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 Formdesk tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

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

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

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "formdesk-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 Formdesk MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Formdesk 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 Formdesk 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 Formdesk 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=['formdesk']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "formdesk-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 Formdesk 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 Formdesk 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 Formdesk MCP Agent with another framework

FAQ

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

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

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

Yes, absolutely. You can configure which Formdesk 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 Formdesk 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.