How to integrate Hostinger MCP with CrewAI

This guide walks you through connecting Hostinger to CrewAI using the Composio tool router. By the end, you'll have a working Hostinger agent that can list all hostinger domain renewals, update dns records for production site, check vps status and resource usage through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Hostinger account through Composio's Hostinger MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Hostinger logoHostinger
Api Key

Hostinger is a web hosting and domain management platform for websites, DNS, domains, billing, and VPS infrastructure. It helps teams manage hosting operations from one place with simple tools and reliable APIs.

24 Tools

Introduction

This guide walks you through connecting Hostinger to CrewAI using the Composio tool router. By the end, you'll have a working Hostinger agent that can list all hostinger domain renewals, update dns records for production site, check vps status and resource usage through natural language commands.

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

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

Also integrate Hostinger with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Hostinger connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Hostinger
  • Build a conversational loop where your agent can execute Hostinger 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 Hostinger MCP server, and what's possible with it?

The Hostinger MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Hostinger account. It provides structured and secure access to your domains, DNS records, hosting services, billing details, and virtual machines, so your agent can check domain availability, review DNS settings, list websites, inspect subscriptions, and monitor hosting resources on your behalf.

  • Domain search and review: Have your agent check whether a domain is available and list the domains already associated with your Hostinger account.
  • DNS record inspection: Instruct your agent to retrieve the DNS records for a domain when you need to review its current configuration.
  • Website and hosting overview: Let the agent list your websites and hosting orders so you can quickly see what you operate through Hostinger.
  • Subscriptions and billing review: Direct your agent to list active subscriptions, available payment methods, and catalog items when reviewing services and costs.
  • Virtual machine and key inventory: Have your agent list your virtual machines and public keys to help you review your VPS resources and access setup.

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

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Hostinger connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
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 crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Hostinger via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

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
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
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 Hostinger MCP URL
6

Create a Composio Tool Router session for Hostinger

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["hostinger"])

url = session.mcp.url
What's happening:
  • You create a Hostinger only session through Composio
  • Composio returns an MCP HTTP URL that exposes Hostinger tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\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"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[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:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["hostinger"],
)
url = session.mcp.url

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

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\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"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

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

Conclusion

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

Supported Tools

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

Check Domain Availability

Check domain availability.

Create VPS Public Key

Create public key.

Create WHOIS Profile

Create a WHOIS contact profile for domain registration.

Delete Public Key

Delete public key.

Generate Free Subdomain

Generate a free subdomain.

Get DNS Records

Tool to retrieve DNS records for a domain.

Get Domain Forwarding

Tool to retrieve domain forwarding configuration.

Get VPS Template Details

Get template details.

Get WHOIS Profile

Get WHOIS profile.

Get WHOIS Profile Usage

Tool to retrieve domain list where provided WHOIS contact profile is used.

List Catalog Items

Get catalog item list.

List VPS Data Centers

Get data center list.

List DNS Snapshots

Tool to retrieve DNS snapshots for a domain.

List Domains

Get domain list.

List Hosting Orders

Tool to list hosting orders.

List Payment Methods

Get payment method list.

List Public Keys

Get public keys.

List Subscriptions

Get subscription list.

List VPS Templates

Get templates.

List Virtual Machines

Get virtual machines.

List Websites

List websites.

List WHOIS Profiles

Retrieve WHOIS contact profiles for domain registration.

Validate DNS Records

Validate DNS records.

Verify Domain Ownership

Verify ownership of a single domain and return the verification status.

FRAMEWORKS

How to build Hostinger MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Hostinger MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Hostinger MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Hostinger MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Hostinger MCP with Claude Cowork

Codex logo

Codex

Use Hostinger MCP with Codex

OpenClaw logo

OpenClaw

Use Hostinger MCP with OpenClaw

Hermes logo

Hermes

Use Hostinger MCP with Hermes

CLI logo

CLI

Use Hostinger MCP with CLI

Google ADK logo

Google ADK

Use Hostinger MCP with Google ADK

LangChain logo

LangChain

Use Hostinger MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Hostinger MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Hostinger MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Hostinger MCP with LlamaIndex

FAQ

Frequently asked questions

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

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

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

Start with Hostinger.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies