# How to integrate Reply io MCP with Autogen

```json
{
  "title": "How to integrate Reply io MCP with Autogen",
  "toolkit": "Reply io",
  "toolkit_slug": "reply_io",
  "framework": "AutoGen",
  "framework_slug": "autogen",
  "url": "https://composio.dev/toolkits/reply_io/framework/autogen",
  "markdown_url": "https://composio.dev/toolkits/reply_io/framework/autogen.md",
  "updated_at": "2026-05-12T10:23:56.407Z"
}
```

## Introduction

This guide walks you through connecting Reply io to AutoGen using the Composio tool router. By the end, you'll have a working Reply io agent that can list all active campaigns this week, show contacts added to sales lists, delete a campaign by campaign id through natural language commands.
This guide will help you understand how to give your AutoGen agent real control over a Reply io account through Composio's Reply io MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Reply io with

- [OpenAI Agents SDK](https://composio.dev/toolkits/reply_io/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/reply_io/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/reply_io/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/reply_io/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/reply_io/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/reply_io/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/reply_io/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/reply_io/framework/cli)
- [Google ADK](https://composio.dev/toolkits/reply_io/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/reply_io/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/reply_io/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/reply_io/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/reply_io/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/reply_io/framework/crew-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 Reply io
- Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
- Configure an Autogen AssistantAgent that can call Reply io tools
- Run a live chat loop where you ask the agent to perform Reply io 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 Reply io MCP server, and what's possible with it?

The Reply io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Reply io account. It provides structured and secure access to your sales engagement platform, so your agent can manage campaigns, handle contacts, organize sequences, and automate routine sales operations on your behalf.
- Campaign and sequence management: Effortlessly list, browse, and delete campaigns or sequences to keep your outreach organized and up to date.
- Contact and list organization: Let your agent fetch, review, and organize your Reply io contacts and contact lists for targeted sales actions.
- Email account administration: Retrieve all connected email accounts or remove outdated ones, making sure your sales tools stay streamlined.
- User and access control: Easily remove users or generate unique identifiers for tasks, maintaining security and clarity in your team’s workflow.
- Automated data retrieval: Quickly pull up paginated lists of campaigns, sequences, email accounts, or contact lists to inform your sales strategies and next steps.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `REPLY_IO_ADD_CONTACT_TO_SEQUENCE` | Add Contact to Sequence | Move an existing contact to a sequence in Reply.io. Use this action to enroll contacts in email sequences for automated outreach campaigns. This action allows you to specify where in the sequence to start, whether to remove the contact from their current sequence, and when to begin processing. |
| `REPLY_IO_ARCHIVE_SEQUENCE` | Archive Sequence | Tool to archive a sequence. Use when you need to archive an existing sequence without permanently deleting it. |
| `REPLY_IO_CLEAR_CONTACT_STATUS` | Clear Contact Status | Tool to clear statuses from contacts. Use when you need to remove specific or all clearable statuses from contacts. |
| `REPLY_IO_CONNECT_EXCHANGE_ACCOUNT` | Connect Exchange Account via OAuth | Tool to initiate OAuth connection for an Exchange email account. Use when you need to connect an Exchange account to Reply.io via OAuth flow. Returns the Microsoft OAuth consent page URL where the user should be redirected. |
| `REPLY_IO_CONNECT_GMAIL_ACCOUNT` | Connect Gmail Account | Tool to initiate Gmail account connection via OAuth. Returns the OAuth authorization URL where the user should be redirected to grant permissions. |
| `REPLY_IO_CREATE_CONTACT` | Create Contact | Tool to create a new contact in Reply.io. Use when adding contacts to your outreach database. |
| `REPLY_IO_CREATE_SEQUENCE_STEP` | Create Sequence Step | Tool to add a new step to an existing sequence. Use when you need to build or modify sequence workflows with Email, Call, Task, SMS, WhatsApp, LinkedIn, Condition, or Zapier steps. |
| `REPLY_IO_DELETE_CONTACT` | Delete Contact | Tool to delete a contact. Use after confirming the contact exists to remove it permanently. |
| `REPLY_IO_DELETE_EMAIL_ACCOUNT` | Delete Email Account | Tool to delete a specific email account. Use when you need to remove an existing email account identified by its ID. |
| `REPLY_IO_DELETE_SCHEDULE` | Delete Schedule | Tool to delete a schedule. Use after confirming the schedule exists to remove it permanently. |
| `REPLY_IO_DELETE_SEQUENCE` | Delete Sequence | Tool to delete a sequence. Use after confirming the sequence exists to remove it permanently. |
| `REPLY_IO_DELETE_USER` | Delete User | Tool to delete a user. Use after confirming the user exists to remove them permanently. |
| `REPLY_IO_GENERATE_ULID` | Generate ULID | Generate ULID |
| `REPLY_IO_GET_CONTACT_BY_ID` | Get Contact by ID | Tool to retrieve a contact by ID. Use when you have a contact ID and need detailed contact information. |
| `REPLY_IO_GET_CONTACT_STATUS` | Get Contact Status | Tool to get contact status. Use when you need to retrieve all current statuses for a contact. |
| `REPLY_IO_GET_CURRENT_USER` | Get Current User | Tool to get the current authenticated user's ID. Use when you need to verify API key validity or identify the current user. |
| `REPLY_IO_GET_DISCONNECTED_EMAIL_ACCOUNTS` | Reply.io Get Disconnected Email Accounts | Tool to list email accounts that are currently disconnected due to authentication or connection errors. Use when you need to identify and troubleshoot problematic email accounts. |
| `REPLY_IO_GET_SEQUENCE_BY_ID` | Get Sequence By ID | Tool to retrieve detailed information about a sequence by its ID. Use when you need to get comprehensive sequence details including settings, email accounts, and workflow steps. |
| `REPLY_IO_GET_SEQUENCE_CONTACTS_EXTENDED` | Get Sequence Contacts Extended | Tool to retrieve all contacts enrolled in a sequence with additional details. Use when you need to see contact engagement status, current step, or completion timestamps within a sequence. |
| `REPLY_IO_GET_SEQUENCE_STEP_BY_ID` | Get Sequence Step by ID | Tool to retrieve details of a specific sequence step. Use when you need to inspect step configuration including type, delays, execution mode, and type-specific settings. |
| `REPLY_IO_LIST_CONTACTS_BASIC` | List Contacts Basic | Tool to list contacts. Use when verifying API access and gathering contact IDs. |
| `REPLY_IO_LIST_EMAIL_ACCOUNTS` | Reply.io List Email Accounts | Tool to list all email accounts. Use when you need to retrieve email accounts page by page. |
| `REPLY_IO_LIST_LISTS` | Reply.io List Lists | Tool to list all contact lists. Use when you need to retrieve all available lists in your Reply.io account. |
| `REPLY_IO_LIST_SEQUENCES` | List Sequences | Tool to retrieve a paginated list of sequences. Use when you need to browse sequences with optional filtering by name. |
| `REPLY_IO_LIST_SEQUENCE_STEPS` | List Sequence Steps | Tool to retrieve all steps in a sequence. Use when you need to get the complete list of steps configured for a specific sequence. |
| `REPLY_IO_PAUSE_SEQUENCE` | Pause Sequence | Tool to pause a running sequence. Use when you need to temporarily stop a sequence from sending emails or executing steps. |
| `REPLY_IO_REMOVE_CONTACT_FROM_SEQUENCE` | Remove Contact From Sequence | Tool to remove a contact from a sequence. Use when you need to stop a contact from receiving further steps in a specific sequence. |
| `REPLY_IO_REMOVE_CONTACTS_FROM_SEQUENCE` | Bulk Remove Contacts from Sequence | Tool to bulk remove multiple contacts from a sequence at once. Use when you need to remove several contacts from a sequence efficiently in a single operation. |
| `REPLY_IO_SEARCH_CONTACTS` | Search Contacts by Email | Tool to search contacts by email. Use when you need to find existing contact IDs for update tests. |
| `REPLY_IO_SET_CONTACT_STATUS` | Set Contact Status | Tool to set the status of one or more contacts. Use when you need to update contact statuses in bulk. |
| `REPLY_IO_START_SEQUENCE` | Start Sequence | Tool to start a sequence. Use when you need to activate a sequence that is in New or Paused status. |
| `REPLY_IO_UPDATE_CONTACT` | Update Contact | Tool to update an existing contact's information. Use when you need to modify contact details. |
| `REPLY_IO_UPDATE_EMAIL_ACCOUNT` | Update Email Account | Tool to update an existing email account with custom SMTP/IMAP settings. Use when you need to modify email account configuration such as sender name, signature, server settings, or daily limits. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Reply io MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Reply io. Instead of manually wiring Reply io APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

You will need:
- A Composio API key
- An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
- A Reply io account you can connect to Composio
- Some basic familiarity with Autogen and Python async

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

Install Composio, Autogen extensions, and dotenv.
What's happening:
- composio connects your agent to Reply io via MCP
- autogen-agentchat provides the AssistantAgent class
- autogen-ext-openai provides the OpenAI model client
- autogen-ext-tools provides MCP workbench support
```bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools
```

### 3. Set up environment variables

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 Reply io connections to use
```bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com
```

### 4. Import dependencies and create Tool Router session

What's happening:
- load_dotenv() reads your .env file
- Composio(api_key=...) initializes the SDK
- create(...) creates a Tool Router session that exposes Reply io tools
- session.mcp.url is the MCP endpoint that Autogen will connect to
```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 Reply io session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["reply_io"]
    )
    url = session.mcp.url
```

### 5. Configure MCP parameters for Autogen

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
```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")}
)
```

### 6. Create the model client and agent

What's happening:
- OpenAIChatCompletionClient wraps the OpenAI model for Autogen
- McpWorkbench connects the agent to the MCP tools
- AssistantAgent is configured with the Reply io tools from the workbench
```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 Reply io assistant agent with MCP tools
    agent = AssistantAgent(
        name="reply_io_assistant",
        description="An AI assistant that helps with Reply io operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )
```

### 7. Run the interactive chat loop

What's happening:
- The script prompts you in a loop with You:
- Autogen passes your input to the model, which decides which Reply io 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
```python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Reply io 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")
```

## Complete Code

```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 Reply io session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["reply_io"]
    )
    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 Reply io assistant agent with MCP tools
        agent = AssistantAgent(
            name="reply_io_assistant",
            description="An AI assistant that helps with Reply io 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 Reply io 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 Reply io 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 Reply io, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

## How to build Reply io MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/reply_io/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/reply_io/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/reply_io/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/reply_io/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/reply_io/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/reply_io/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/reply_io/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/reply_io/framework/cli)
- [Google ADK](https://composio.dev/toolkits/reply_io/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/reply_io/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/reply_io/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/reply_io/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/reply_io/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/reply_io/framework/crew-ai)

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.
- [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Reply io MCP?

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

### Can I use Tool Router MCP with Autogen?

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 Reply io tools.

### Can I manage the permissions and scopes for Reply io while using Tool Router?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
