# How to integrate DEV Community MCP with Vercel AI SDK v6

```json
{
  "title": "How to integrate DEV Community MCP with Vercel AI SDK v6",
  "toolkit": "DEV Community",
  "toolkit_slug": "devto",
  "framework": "Vercel AI SDK",
  "framework_slug": "ai-sdk",
  "url": "https://composio.dev/toolkits/devto/framework/ai-sdk",
  "markdown_url": "https://composio.dev/toolkits/devto/framework/ai-sdk.md",
  "updated_at": "2026-06-18T09:25:59.372Z"
}
```

## Introduction

This guide walks you through connecting DEV Community to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working DEV Community agent that can list your published dev articles, draft a tutorial post about docker, find trending javascript posts on dev through natural language commands.
This guide will help you understand how to give your Vercel AI SDK agent real control over a DEV Community account through Composio's DEV Community MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate DEV Community with

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

## TL;DR

Here's what you'll learn:
- How to set up and configure a Vercel AI SDK agent with DEV Community integration
- Using Composio's Tool Router to dynamically load and access DEV Community tools
- Creating an MCP client connection using HTTP transport
- Building an interactive CLI chat interface with conversation history management
- Handling tool calls and results within the Vercel AI SDK framework

## What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.
Key features include:
- streamText: Core function for streaming responses with real-time tool support
- MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
- Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
- OpenAI Provider: Native integration with OpenAI models

## What is the DEV Community MCP server, and what's possible with it?

The DEV Community MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your DEV Community account. It provides structured and secure access so your agent can perform DEV Community operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `DEVTO_CREATE_ARTICLE` | Create Article | Create a new article on DEV Community. Use this action to create a new article on behalf of the authenticated user. The article can be published immediately by setting published=true, or saved as a draft by setting published=false (which is the default). Required fields are title and body_markdown. Optional fields include description, main_image, tags, series, canonical_url, and organization_id. |
| `DEVTO_GET_ARTICLE` | Get Article By ID | Returns a single published article by its ID, including full body content. Use this action when you know the unique ID of the article you want to retrieve. The response includes complete article details such as title, full HTML and markdown body content, author information, reaction counts, comments count, and reading time. |
| `DEVTO_GET_ARTICLE_BY_PATH` | Get Article By Path | Returns a single published article by username and slug path. Use this action when you know the username of the author and the article's slug. The response includes full article details including title, content, author info, reactions count, comments count, and reading time. |
| `DEVTO_GET_COMMENT` | Get Comment by ID | Returns a single comment and its descendants (replies) by comment ID. Use this action when you need to retrieve a specific comment along with all its replies from DEV Community. The response includes the comment content, author information, and nested child comments. Note: The comment ID is the id_code field (e.g., "1", "32k5a"), not the numeric user_id. |
| `DEVTO_GET_CURRENT_USER` | Get Current User | Tool to get the currently authenticated user's profile information. Use when you need to retrieve the profile of the user associated with the provided API key. Returns user details including username, name, bio, location, and profile image. |
| `DEVTO_GET_LISTING` | Get Listing | Returns a single classified listing by its ID. Use this action to retrieve detailed information about a specific listing on DEV Community, including the title, description, category, tags, and information about the user who posted it. |
| `DEVTO_GET_ORGANIZATION` | Get Organization | Returns a single organization by its username. Use this action when you need to retrieve organization profile information from DEV Community. Returns organization details including name, summary, social links, and profile image. |
| `DEVTO_GET_PROFILE_IMAGE` | Get Profile Image | Returns the profile image URL for a user or organization by username. Use this action to retrieve the profile picture(s) for a specific user or organization on DEV Community. The API returns both the full-size image URL and a 90px thumbnail. |
| `DEVTO_GET_USER` | Get user | Tool to get a single user by their ID or username. Use when you need to retrieve user profile information from DEV Community. Returns user details including username, name, bio, location, and profile image. |
| `DEVTO_LIST_ARTICLES` | List Articles | Returns a list of published articles, optionally filtered by tags, username, state, or top articles. Supports pagination. Use when you need to browse or search for articles on DEV Community. Examples: - Get latest articles: omit all filters - Get articles by tag: set tag="javascript" - Get top articles: set state="all" and top=7 - Get rising articles: set state="rising" - Get articles from user: set username="ben" |
| `DEVTO_LIST_COMMENTS` | List Comments | Tool to list comments for a specified article or podcast episode on DEV Community. Use when you need to retrieve all comments for a particular article or podcast episode. Requires either a_id (article ID) or p_id (podcast episode ID) parameter. |
| `DEVTO_LIST_FOLLOWED_TAGS` | List Followed Tags | Returns a list of tags followed by the authenticated user. Use this action to retrieve the tags that the currently authenticated user has followed on DEV.to. The response includes the tag ID, name, and points. |
| `DEVTO_LIST_FOLLOWERS` | List Followers | Tool to retrieve a list of users who follow the authenticated user. Supports pagination with 80 followers per page by default. Use when you need to see who is following the authenticated user's profile. |
| `DEVTO_LIST_LATEST_ARTICLES` | List latest DEV Community articles | Tool to retrieve a list of published articles sorted by descending publish date. Use when you need to fetch the latest articles from DEV Community with pagination support. Returns articles with full details including author info, tags, and engagement metrics. |
| `DEVTO_LIST_LISTINGS` | List Listings | Returns a list of classified listings for jobs, mentors, products, etc. Use this action to browse available listings on DEV Community. Supports pagination and filtering by category to find specific types of listings (jobs, mentors, events, etc.). |
| `DEVTO_LIST_LISTINGS_BY_CATEGORY` | List Listings By Category | Returns a list of classified listings filtered by category. Use this action to browse listings on DEV Community for a specific category (jobs, mentors, products, events, etc.). The category is a required path parameter. Supports pagination via page and per_page parameters. |
| `DEVTO_LIST_ORGANIZATION_ARTICLES` | List Organization Articles | Tool to list articles published by a specific organization on DEV.to. Use when you need to retrieve all articles published by an organization. The results are paginated and can be filtered by page number and items per page. |
| `DEVTO_LIST_ORGANIZATION_USERS` | List organization users on DEV.to | Tool to list users belonging to a specified organization on DEV.to. Use when you need to retrieve all members/users of a particular organization. Returns a list of user objects with their profile information including username, name, profile image, and social links. |
| `DEVTO_LIST_PODCAST_EPISODES` | List podcast episodes on DEV.to | Tool to retrieve a list of podcast episodes from DEV.to. Use when you need to browse or search for podcast episodes on DEV.to. Returns a list of podcast episodes, optionally filtered by podcast username. Supports pagination to navigate through large result sets. |
| `DEVTO_LIST_READING_LIST` | List DEVTO Reading List | Returns the articles in the authenticated user's reading list. Requires authentication via API key. The reading list contains articles that the authenticated user has saved for later reading. |
| `DEVTO_LIST_TAGS` | List Tags | Returns a list of tags with their names, background colors, and text colors. Use this action to retrieve available tags from DEV Community for filtering articles or discovering topics. Supports pagination to handle large numbers of tags. |
| `DEVTO_LIST_USER_ALL_ARTICLES` | List User All Articles | Tool to list all articles (both published and unpublished) for the authenticated user. Use when you need to retrieve all articles belonging to the authenticated user's account, including draft and unpublished articles. |
| `DEVTO_LIST_USER_ARTICLES` | List User Articles | Tool to list published articles for the authenticated user. Use when you need to retrieve only the published articles belonging to the authenticated user's account. For unpublished/draft articles, use the List User All Articles action instead. |
| `DEVTO_LIST_USER_PUBLISHED_ARTICLES` | List user's published articles | Returns a list of the authenticated user's published articles only. Use when you need to retrieve articles that the current user has published on DEV Community. Supports pagination via page and per_page parameters. |
| `DEVTO_LIST_USER_UNPUBLISHED_ARTICLES` | List user's unpublished articles | Returns a list of the authenticated user's unpublished (draft) articles. Use when you need to retrieve draft articles that have not yet been published. Supports pagination via page and per_page parameters. |
| `DEVTO_LIST_VIDEOS` | List Videos | Tool to retrieve a list of articles that contain videos. Use when you need to browse video content on DEV Community. Supports pagination via page and per_page parameters. |
| `DEVTO_UPDATE_ARTICLE` | Update Article | Update an existing article on DEV Community. Only the article owner can update it. Use this action to modify article properties like title, body content, description, cover image, tags, and publication status. Only provide the fields you want to update. |
| `DEVTO_UPDATE_LISTING` | Update Listing | Updates an existing classified listing on DEV Community. Use this action to modify a listing's title, body, category, tags, or status. The 'bump' action refreshes the listing's timestamp, 'publish' sets it to published, and 'unpublish' sets it to unpublished. Requires API key authentication. |

## Supported Triggers

None listed.

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

The DEV Community MCP server is an implementation of the Model Context Protocol that connects your AI agent to DEV Community. It provides structured and secure access so your agent can perform DEV Community operations on your behalf through a secure, permission-based interface.
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

Before you begin, make sure you have:
- Node.js and npm installed
- A Composio account with API key
- An OpenAI API key

### 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 required dependencies

First, install the necessary packages for your project.
What you're installing:
- @ai-sdk/openai: Vercel AI SDK's OpenAI provider
- @ai-sdk/mcp: MCP client for Vercel AI SDK
- @composio/core: Composio SDK for tool integration
- ai: Core Vercel AI SDK
- dotenv: Environment variable management
```bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's needed:
- OPENAI_API_KEY: Your OpenAI API key for GPT model access
- COMPOSIO_API_KEY: Your Composio API key for tool access
- COMPOSIO_USER_ID: A unique identifier for the user session
```bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
```

### 4. Import required modules and validate environment

What's happening:
- We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
- The dotenv/config import automatically loads environment variables
- The MCP client import enables connection to Composio's tool server
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});
```

### 5. Create Tool Router session and initialize MCP client

What's happening:
- We're creating a Tool Router session that gives your agent access to DEV Community tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
- This session provides access to all DEV Community-related tools through the MCP protocol
```typescript
async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["devto"],
  });

  const mcpUrl = session.mcp.url;
```

### 6. Connect to MCP server and retrieve tools

What's happening:
- We're creating an MCP client that connects to our Composio Tool Router session via HTTP
- The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
- The type: "http" is important - Composio requires HTTP transport
- tools() retrieves all available DEV Community tools that the agent can use
```typescript
const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();
```

### 7. Initialize conversation and CLI interface

What's happening:
- We initialize an empty messages array to maintain conversation history
- A readline interface is created to accept user input from the command line
- Instructions are displayed to guide the user on how to interact with the agent
```typescript
let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to devto, like summarize my last 5 emails, send an email, etc... :)))\n",
);

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();
```

### 8. Handle user input and stream responses with real-time tool feedback

What's happening:
- We use streamText instead of generateText to stream responses in real-time
- toolChoice: "auto" allows the model to decide when to use DEV Community tools
- stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
- onStepFinish callback displays which tools are being used in real-time
- We iterate through the text stream to create a typewriter effect as the agent responds
- The complete response is added to conversation history to maintain context
- Errors are caught and displayed with helpful retry suggestions
```typescript
rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
```

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["devto"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to devto, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
      console.log("\nGoodbye!");
      rl.close();
      process.exit(0);
    }

    if (!trimmedInput) {
      rl.prompt();
      return;
    }

    messages.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
```

## Conclusion

You've successfully built a DEV Community agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.
Key features of this implementation:
- Real-time streaming responses for a better user experience with typewriter effect
- Live tool execution feedback showing which tools are being used as the agent works
- Dynamic tool loading through Composio's Tool Router with secure authentication
- Multi-step tool execution with configurable step limits (up to 10 steps)
- Comprehensive error handling for robust agent execution
- Conversation history maintenance for context-aware responses
You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build DEV Community MCP Agent with another framework

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

## Related Toolkits

- [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide.
- [Instagram](https://composio.dev/toolkits/instagram) - Instagram is a social platform for sharing photos, videos, and stories with your audience. It helps brands and creators engage, grow, and analyze their online presence.
- [Ayrshare](https://composio.dev/toolkits/ayrshare) - Ayrshare is a Social Media API for managing, automating, and analyzing posts across multiple platforms. It helps you streamline social media workflows and centralize analytics.
- [Dotsimple](https://composio.dev/toolkits/dotsimple) - Dotsimple is a social media management platform for planning, creating, and publishing content. It helps teams boost their reach with AI-powered content generation and actionable analytics.
- [Strava](https://composio.dev/toolkits/strava) - Strava is a social fitness network and app for cyclists and runners. It's perfect for tracking workouts, sharing progress, and joining active communities.
- [Tiktok](https://composio.dev/toolkits/tiktok) - Tiktok is a short-form video platform for creating, sharing, and discovering viral content. It helps creators and brands reach massive audiences with creative tools and global social features.
- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and DEV Community MCP?

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

### Can I use Tool Router MCP with Vercel AI SDK v6?

Yes, you can. Vercel AI SDK v6 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 DEV Community tools.

### Can I manage the permissions and scopes for DEV Community while using Tool Router?

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

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