SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Wit ai MCP with Autogen

Connect Autogen to Wit ai MCP. Analyze user message for intent and entities, list all custom traits in your wit app, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Wit ai logoWit ai
Api Key

Wit.ai is a natural language processing platform that turns text or speech into structured data. It's perfect for building voice and chat interfaces that truly understand users.

31 Tools

Introduction

This guide walks you through connecting Wit ai to AutoGen using the Composio tool router. By the end, you'll have a working Wit ai agent that can create and manage apps, define intents and entities, train with utterances, parse messages, and detect languages through natural language commands.

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

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

Also integrate Wit ai with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the required dependencies for Autogen and Composio
  • Initialize Composio and create a Tool Router session for Wit ai
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Wit ai tools
  • Run a live chat loop where you ask the agent to perform Wit ai operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

  • Multi-Agent Systems: Build collaborative agent workflows
  • MCP Workbench: Native support for Model Context Protocol tools
  • Streaming HTTP: Connect to external services through streamable HTTP
  • AssistantAgent: Pre-built agent class for tool-using assistants

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

The Wit ai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Wit ai account. It provides structured and secure access to your NLP resources, so your agent can create and manage apps, analyze natural language, organize intents and traits, and update configurations on your behalf.

  • Instant natural language analysis: Let your agent extract intents, entities, and traits from any text message using Wit.ai’s advanced NLP engine.
  • Automated app management: Easily create, update, or delete Wit.ai apps, enabling rapid deployment and maintenance of your language models.
  • Intent and trait organization: Have your agent list, retrieve details, or update all defined intents and traits, keeping your language understanding models organized and up to date.
  • Full app metadata access: Fetch comprehensive app settings and metadata for better monitoring, debugging, or auditing of your NLP solutions.
  • Seamless entity and trait customization: Programmatically add or configure traits for tailored entity recognition and improved intent matching.

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

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Wit ai account you can connect to Composio
  • Some basic familiarity with Autogen and Python async
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 python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Wit ai via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

4

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

  • COMPOSIO_API_KEY is required to talk to Composio
  • OPENAI_API_KEY is used by Autogen's OpenAI client
  • USER_ID is how Composio identifies which user's Wit ai connections to use
5

Import dependencies and create Tool Router session

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Wit ai session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["wit_ai"]
    )
    url = session.mcp.url
What's happening:
  • load_dotenv() reads your .env file
  • Composio(api_key=...) initializes the SDK
  • create(...) creates a Tool Router session that exposes Wit ai tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to
6

Configure MCP parameters for Autogen

python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

  • url points to the Tool Router MCP endpoint from Composio
  • timeout is the HTTP timeout for requests
  • sse_read_timeout controls how long to wait when streaming responses
  • terminate_on_close=True cleans up the MCP server process when the workbench is closed
7

Create the model client and agent

python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Wit ai assistant agent with MCP tools
    agent = AssistantAgent(
        name="wit_ai_assistant",
        description="An AI assistant that helps with Wit ai operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Wit ai tools from the workbench
8

Run the interactive chat loop

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

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

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

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
What's happening:
  • The script prompts you in a loop with You:
  • Autogen passes your input to the model, which decides which Wit ai tools to call via MCP
  • agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
  • Typing exit, quit, or bye ends the loop

Complete Code

Here's the complete code to get you started with Wit ai and AutoGen:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Wit ai session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["wit_ai"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Wit ai assistant agent with MCP tools
        agent = AssistantAgent(
            name="wit_ai_assistant",
            description="An AI assistant that helps with Wit ai operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

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

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

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

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

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

Conclusion

You now have an Autogen assistant wired into Wit ai through Composio's Tool Router and MCP. From here you can:
  • Add more toolkits to the toolkits list, for example notion or hubspot
  • Refine the agent description to point it at specific workflows
  • Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Wit ai, you can reuse the same structure for other MCP-enabled apps with minimal code changes.
TOOLS

Supported Tools

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

Add Entity Keyword

Tool to add a keyword with optional synonyms to a Wit.

Add Keyword Synonym

Tool to add a new synonym to a keyword in an entity.

Add Value to Trait

Tool to add a new value to an existing trait in Wit.

Create Wit.ai App

Tool to create a new app in Wit.

Create Wit.ai Entity

Tool to create a new entity in Wit.

Create Wit.ai Intent

Tool to create a new intent in Wit.

Create Wit.ai Trait

Create a new Wit.

Create Wit.ai Training Utterances

Tool to add training utterances (samples with annotations) to your Wit.

Delete App

Tool to delete a specific app from wit.

Delete Entity

Tool to permanently delete an entity by name.

Delete Entity Keyword

Tool to delete a keyword from a keywords entity in wit.

Delete Entity Role

Tool to delete a specific role from an entity in wit.

Delete Intent

Tool to permanently delete an intent by name.

Delete Keyword Synonym

Tool to delete a synonym from a keyword in an entity.

Delete Utterances

Tool to delete validated utterances (training samples) from your Wit.

Wit.ai Detect Language

Tool to detect the language of a given text input.

Export App Data

Tool to export Wit.

Get App Details

Retrieve metadata and settings for a Wit.

Get Entity Details

Tool to retrieve details of a specific entity including keywords and roles.

Get Intent Details

Tool to retrieve details of a specific intent.

Get Intents

List intents in a Wit.

Wit.ai Get Message

Tool to analyze a text message and extract its intent, entities, and traits.

Get Trait Details

Tool to retrieve details of a specific trait.

List Traits

Tool to list all traits in a Wit.

Get Voice Details

Tool to retrieve details for a specific text-to-speech voice.

List Wit.ai Apps

List Wit.

List App Tags

Tool to retrieve all tag groups (versions) for a Wit.

List Entities

Tool to list all entities in a Wit.

List Utterances

Tool to retrieve training utterances (samples) from a Wit.

List Voices

Tool to retrieve all available text-to-speech voices grouped by locale.

Update Wit.ai App

Tool to update an existing Wit.

FRAMEWORKS

How to build Wit ai MCP Agent with another framework

Claude Code logo

Claude Code

Use Wit ai MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Wit ai MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Wit ai MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Wit ai MCP with Claude Agent SDK

Codex logo

Codex

Use Wit ai MCP with Codex

OpenClaw logo

OpenClaw

Use Wit ai MCP with OpenClaw

Hermes logo

Hermes

Use Wit ai MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Wit ai MCP with Atomic Agent

Google ADK logo

Google ADK

Use Wit ai MCP with Google ADK

LangChain logo

LangChain

Use Wit ai MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Wit ai MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Wit ai MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Wit ai MCP with LlamaIndex

CrewAI logo

CrewAI

Use Wit ai MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Wit ai MCP with Pydantic AI

FAQ

Frequently asked questions

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

Yes, you can. Autogen 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 Wit ai tools.

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

Start with Wit ai.It takes 30 seconds.

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

Start building