How to integrate Geocodio MCP with CrewAI

Framework Integration Gradient
Geocodio Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Geocodio to CrewAI using the Composio tool router. By the end, you'll have a working Geocodio agent that can convert a list of addresses to coordinates, find school district for a specific address, reverse geocode multiple latitude,longitude pairs, append census data to validated addresses through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Geocodio account through Composio's Geocodio 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 a Composio API key and configure your Geocodio connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Geocodio
  • Build a conversational loop where your agent can execute Geocodio 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 Geocodio MCP server, and what's possible with it?

The Geocodio MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Geocodio account. It provides structured and secure access to geocoding, reverse geocoding, and data enrichment features for US and Canadian locations, so your agent can look up coordinates, convert addresses, and append valuable geographic or demographic data on your behalf.

  • Address geocoding and reverse geocoding: Instantly convert street addresses to latitude/longitude coordinates and vice versa, including single or batch operations for entire address lists or coordinate sets.
  • Geographic and demographic data enrichment: Automatically append detailed information like Congressional Districts, Census block/tract FIPS codes, metropolitan area codes, and school districts to your geocoded addresses.
  • Canadian-specific data augmentation: Enhance results with Canadian provincial electoral districts and official Statistics Canada boundaries for any Canadian address.
  • FFIEC Fair Lending data integration: Have your agent enrich addresses with federal lending and demographic metrics for compliance, analytics, or reporting.
  • Automated list and data management: Create, enrich, or delete geocoded lists, empowering your agent to handle large-scale address and location workflows efficiently.

Supported Tools & Triggers

Tools
Append Canadian StatCan BoundariesTool to append Canadian statistical boundaries from Statistics Canada.
Append Canadian Provincial Electoral DistrictTool to append Canadian provincial electoral district to geocode results.
Append Census Data to Geocoded AddressTool to append Census block/tract FIPS and MSA/CSA codes to geocoded addresses.
Append Congressional DistrictTool to append Congressional District information to a geocoded address.
Delete Geocodio ListTool to delete a specific list.
Append FFIEC Fair Lending DataTool to append FFIEC (Fair Lending) data to a geocoded address.
Batch Reverse GeocodeTool to batch reverse geocode up to 10,000 coordinates in one request.
Single Reverse GeocodeTool to reverse geocode a single coordinate.
Get Coordinates for Batch Reverse GeocodeTool to provide a predefined set of latitude,longitude strings.
Append School DistrictTool to append School District information to a geocoded address.
Single Forward GeocodeTool to forward geocode a single address.
Append State Legislative DistrictTool to append state legislative district information to a geocoded address.
Append TimezoneTool to append timezone information to geocode results.
USPS ZIP+4 AppendTool to append USPS ZIP+4 information to US addresses.

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, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Geocodio connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

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

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

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

Import dependencies

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional import if you plan to adapt tools
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()
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 Geocodio MCP URL

Create a Composio Tool Router session for Geocodio

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["geocodio"],
)
url = session.mcp.url
What's happening:
  • You create a Geocodio only session through Composio
  • Composio returns an MCP HTTP URL that exposes Geocodio tools

Configure the LLM

python
llm = LLM(
    model="gpt-5-mini",
    api_key=os.getenv("OPENAI_API_KEY"),
)
What's happening:
  • CrewAI will call this LLM for planning and responses
  • You can swap in a different model if needed

Attach the MCP server and create the agent

python
toolkit_agent = Agent(
    role="Geocodio Assistant",
    goal="Help users interact with Geocodio through natural language commands",
    backstory=(
        "You are an expert assistant with access to Geocodio tools. "
        "You can perform various Geocodio operations on behalf of the user."
    ),
    mcps=[
        MCPServerHTTP(
            url=url,
            streamable=True,
            cache_tools_list=True,
            headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
        ),
    ],
    llm=llm,
    verbose=True,
    max_iter=10,
)
What's happening:
  • MCPServerHTTP connects the agent to the Geocodio MCP endpoint
  • cache_tools_list saves a tools catalog for faster subsequent runs
  • verbose helps you see what the agent is doing

Add a REPL loop with Task and Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to perform Geocodio operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
            f"Current user request: {user_input}\n\n"
            f"Please help the user with their Geocodio related request."
        ),
        expected_output="A helpful response addressing the user's request",
        agent=toolkit_agent,
    )

    crew = Crew(
        agents=[toolkit_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:
  • You build a simple chat loop and keep a running context
  • Each user turn becomes a Task handled by the same agent
  • Crew executes the task and returns a response

Run the application

python
if __name__ == "__main__":
    main()
What's happening:
  • Standard Python entry point so you can run python crewai_geocodio_agent.py

Complete Code

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

python
# file: crewai_geocodio_agent.py
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()

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

    # Configure LLM
    llm = LLM(
        model="gpt-5-mini",
        api_key=os.getenv("OPENAI_API_KEY"),
    )

    # Create Geocodio assistant agent
    toolkit_agent = Agent(
        role="Geocodio Assistant",
        goal="Help users interact with Geocodio through natural language commands",
        backstory=(
            "You are an expert assistant with access to Geocodio tools. "
            "You can perform various Geocodio operations on behalf of the user."
        ),
        mcps=[
            MCPServerHTTP(
                url=url,
                streamable=True,
                cache_tools_list=True,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
            ),
        ],
        llm=llm,
        verbose=True,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Try asking the agent to perform Geocodio operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
                f"Current user request: {user_input}\n\n"
                f"Please help the user with their Geocodio related request."
            ),
            expected_output="A helpful response addressing the user's request",
            agent=toolkit_agent,
        )

        crew = Crew(
            agents=[toolkit_agent],
            tasks=[task],
            verbose=False,
        )

        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

if __name__ == "__main__":
    main()

Conclusion

You now have a CrewAI agent connected to Geocodio through Composio's Tool Router. The agent can perform Geocodio 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

How to build Geocodio MCP Agent with another framework

FAQ

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

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

Can I use Tool Router MCP with CrewAI?

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

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

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