# How to integrate Countdown api MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Countdown api MCP with Vercel AI SDK v6", "toolkit": "Countdown api", "toolkit_slug": "countdown_api", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/countdown_api/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/countdown_api/framework/ai-sdk.md", "updated_at": "2026-05-12T10:07:41.168Z" } ``` ## Introduction This guide walks you through connecting Countdown api to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Countdown api agent that can list all your ebay data collections, start processing requests for a collection, get autocomplete suggestions for 'wireless earbuds' through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Countdown api account through Composio's Countdown api MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Countdown api with - [OpenAI Agents SDK](https://composio.dev/toolkits/countdown_api/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/countdown_api/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/countdown_api/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/countdown_api/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/countdown_api/framework/codex) - [OpenClaw](https://composio.dev/toolkits/countdown_api/framework/openclaw) - [Hermes](https://composio.dev/toolkits/countdown_api/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/countdown_api/framework/cli) - [Google ADK](https://composio.dev/toolkits/countdown_api/framework/google-adk) - [LangChain](https://composio.dev/toolkits/countdown_api/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/countdown_api/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/countdown_api/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/countdown_api/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Countdown api integration - Using Composio's Tool Router to dynamically load and access Countdown api 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 Countdown api MCP server, and what's possible with it? The Countdown api MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Countdown api account. It provides structured and secure access to real-time eBay marketplace data, so your agent can perform actions like searching eBay products, managing collections, retrieving seller feedback, and automating product data workflows on your behalf. - eBay product search and autocomplete: Instantly fetch eBay autocomplete suggestions and help agents surface relevant product search terms and ideas in real time. - Collection management and orchestration: Create, update, list, or delete collections to batch and organize multiple eBay data requests for streamlined marketplace analysis. - Automated collection processing: Start or clear queued requests within a collection, making it easy to control and automate data gathering operations from eBay. - Destination setup and notifications: Set up or remove destinations for results and notifications, ensuring your agent can manage where and how you receive processed eBay data. - Access to rich eBay metadata: Retrieve detailed collection information, product details, customer reviews, and seller feedback to power analytics and business decisions. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `COUNTDOWN_API_CLEAR_ALL_REQUESTS` | Clear Collection Requests | Clears (removes) all pending requests from a collection. Use this to reset a collection before adding new requests, or to cancel all queued requests. The collection must be in 'idle' status. Returns the updated collection details after clearing. | | `COUNTDOWN_API_COLLECTIONS_CREATE_COLLECTION` | Create a new collection | Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule. | | `COUNTDOWN_API_COLLECTIONS_GET_COLLECTION` | Get Collection | Tool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID. | | `COUNTDOWN_API_COLLECTIONS_LIST_COLLECTIONS` | List Collections | Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints. | | `COUNTDOWN_API_COLLECTIONS_START_COLLECTION` | Start Collection | Start processing a collection's queued requests on the Countdown API. Use this tool to manually trigger a collection to begin executing its requests. The collection must have at least one request added to it before it can be started. You need sufficient API credits to run all requests in the collection. Prerequisites: - Collection must exist (use List Collections or Create Collection first) - Collection must have at least one request added - Sufficient API credits available for the number of requests - Collection must not already be running | | `COUNTDOWN_API_COLLECTIONS_UPDATE_COLLECTION` | Update an existing collection | Update an existing collection's settings. Use this to modify collection properties like name, schedule, priority, notification settings, or enabled status. The collection_id must be obtained from list_collections or create_collection. Only specified fields are updated; omitted fields retain their current values. | | `COUNTDOWN_API_CORE_API_SEND_REQUEST` | eBay Autocomplete | Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API. | | `COUNTDOWN_API_CREATE_COLLECTION_REQUEST` | Create Collection Request | Tool to create new requests within a collection for bulk eBay data retrieval. Use when you need to add search, product, reviews, or other eBay data queries to a collection that will be executed on schedule. Collections must be in 'idle' status to accept new requests. | | `COUNTDOWN_API_CREATE_DESTINATION` | Create Destination | Creates a cloud storage destination where batch result sets will be automatically uploaded. Supports Amazon S3, S3-compatible services (MinIO, DigitalOcean Spaces), Google Cloud Storage, Microsoft Azure Blob Storage, and Alibaba Cloud OSS. When enabled=true, the API validates credentials by uploading and deleting a test file. Set enabled=false to create the destination without credential validation. | | `COUNTDOWN_API_DELETE_COLLECTION` | Delete Collection | Tool to delete a collection and its configuration by ID. Use when you need to remove an existing, non-running collection. | | `COUNTDOWN_API_DELETE_DESTINATION` | Delete Destination | Tool to delete a destination by ID. Use when you need to remove an existing destination. | | `COUNTDOWN_API_DELETE_SINGLE_REQUEST` | Delete Single Request | Delete a specific request from a Countdown API collection by its ID. Use this to remove individual requests that are no longer needed. The collection must not be running when deleting requests. | | `COUNTDOWN_API_DESTINATIONS_LIST_DESTINATIONS` | List Destinations | Tool to list all destinations configured for the account. Use when you need to inspect or paginate through configured destinations. | | `COUNTDOWN_API_FIND_COLLECTION_REQUESTS` | Find Collection Requests | Tool to find requests in a collection by custom_id or search query. Use when you need to search for specific requests within a collection using either an exact custom_id match or a text search query. | | `COUNTDOWN_API_GET_ACCOUNT` | Get Account Information | Tool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user. | | `COUNTDOWN_API_LIST_ERROR_LOGS` | List Error Logs | Tool to list error logs from collection executions. Returns recent errors encountered during request processing with details about failed requests and their causes. | | `COUNTDOWN_API_REQUESTS_EXPORT_CSV` | Export Requests CSV | Export all requests from a collection as downloadable CSV files. Returns URLs to CSV files containing the request data. Use this tool when you need to bulk export or download collection request data in CSV format. The response includes paginated download links if the collection has many requests. Collections with no requests will return an empty pages array. | | `COUNTDOWN_API_REQUESTS_EXPORT_JSON` | Export Requests as JSON | Tool to download all requests in a collection as JSON. Use when you need to export the entire request history for a collection. | | `COUNTDOWN_API_REQUESTS_UPDATE_SINGLE_REQUEST` | Update Single Request | Tool to modify parameters of an existing request in a collection. Use when the collection is not running and you need to update eBay Product Data API parameters. | | `COUNTDOWN_API_RESULTS_GET_RESULT_SET` | Get Result Set | Tool to retrieve a collection run's result set payload. Use after a collection run completes to fetch metadata and download links. | | `COUNTDOWN_API_RESULTS_LIST_RESULT_SETS` | List Result Sets | Tool to list result sets produced by a collection. Use when you need to retrieve all summary status of result sets generated by a collection within the 14-day retention window. | | `COUNTDOWN_API_RESULTS_RESEND_RESULT_SET_WEBHOOK` | Resend Result Set Webhook | Resend the webhook notification for a collection's result set. Use this tool to retry webhook delivery when the original webhook POST failed or timed out. The collection must have a notification_webhook URL configured (either on the collection itself or on the account profile). Result sets are only available for 14 days after creation. Prerequisites: - Collection must exist with a valid notification_webhook URL configured - Result set must exist and not be expired (14-day retention) - Use List Result Sets to find valid result_set_id values | | `COUNTDOWN_API_STOP_ALL_COLLECTIONS` | Stop All Collections | Tool to stop all collections. Use when you need to halt any running or queued collections after reviewing operations. | | `COUNTDOWN_API_STOP_COLLECTION` | Stop Collection | Tool to stop (pause) a single collection’s processing by ID. Use when you need to halt a running or queued collection after confirming the target collection ID. | | `COUNTDOWN_API_UPDATE_DESTINATION` | Update Destination | Tool to update a destination's configuration by ID. Use after creating or retrieving a destination to modify its settings. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Countdown api MCP server is an implementation of the Model Context Protocol that connects your AI agent to Countdown api. It provides structured and secure access so your agent can perform Countdown api 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 Countdown api 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 Countdown api-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: ["countdown_api"], }); 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 Countdown api 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 countdown_api, 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 Countdown api 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: ["countdown_api"], }); 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 countdown_api, 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 Countdown api 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 Countdown api MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/countdown_api/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/countdown_api/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/countdown_api/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/countdown_api/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/countdown_api/framework/codex) - [OpenClaw](https://composio.dev/toolkits/countdown_api/framework/openclaw) - [Hermes](https://composio.dev/toolkits/countdown_api/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/countdown_api/framework/cli) - [Google ADK](https://composio.dev/toolkits/countdown_api/framework/google-adk) - [LangChain](https://composio.dev/toolkits/countdown_api/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/countdown_api/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/countdown_api/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/countdown_api/framework/crew-ai) ## Related Toolkits - [Addresszen](https://composio.dev/toolkits/addresszen) - Addresszen is a real-time address autocomplete and verification service. It helps capture accurate, deliverable addresses with instant suggestions and validation. - [Asin data api](https://composio.dev/toolkits/asin_data_api) - Asin data api gives you detailed, real-time product data from Amazon, including price, rank, and reviews. Perfect for e-commerce pros and data-driven marketers who need instant marketplace insights. - [Baselinker](https://composio.dev/toolkits/baselinker) - BaseLinker is an all-in-one e-commerce management platform connecting stores, marketplaces, carriers, and more. It streamlines order processing, inventory control, and automates your sales operations. - [Bestbuy](https://composio.dev/toolkits/bestbuy) - Best Buy is a leading retailer offering APIs for product, store, and recommendation data. Instantly access up-to-date retail insights for smarter shopping and decision-making. - [Btcpay server](https://composio.dev/toolkits/btcpay_server) - BTCPay Server is a free, open-source, self-hosted Bitcoin payment processor. It lets merchants accept Bitcoin payments directly, cutting out middlemen and boosting privacy. - [Cdr platform](https://composio.dev/toolkits/cdr_platform) - Cdr platform is an API for purchasing carbon dioxide removal services. It enables businesses to offset emissions by accessing verified carbon removal projects. - [Cloudcart](https://composio.dev/toolkits/cloudcart) - CloudCart is an e-commerce platform for building and managing online stores. It helps businesses streamline product listings, orders, and customer engagement. - [Dpd2](https://composio.dev/toolkits/dpd2) - Dpd2 is a robust email management platform for handling, sorting, and automating email workflows. Streamline your communications and boost productivity with advanced sorting, labeling, and response tools. - [Finerworks](https://composio.dev/toolkits/finerworks) - FinerWorks is an online platform for fine art and photo printing services. Artists and photographers use it to order custom prints and manage print inventory efficiently. - [Fingertip](https://composio.dev/toolkits/fingertip) - Fingertip is a business management platform for selling, booking, and customer engagement—all from a single link. It helps businesses streamline operations and connect with customers across social channels. - [Fraudlabs pro](https://composio.dev/toolkits/fraudlabs_pro) - FraudLabs Pro is an online payment fraud detection service for e-commerce and merchants. It helps minimize chargebacks and revenue loss by detecting and preventing fraudulent transactions. - [Gift up](https://composio.dev/toolkits/gift_up) - Gift Up! is a digital platform for selling, managing, and redeeming gift cards online. It streamlines promotions and gift card transactions for businesses and their customers. - [Goody](https://composio.dev/toolkits/goody) - Goody is a gifting platform that lets users send gifts and physical products without handling logistics. It streamlines gifting by managing delivery, fulfillment, and recipient experience. - [Gumroad](https://composio.dev/toolkits/gumroad) - Gumroad is a platform for selling digital products, physical goods, and memberships with a simple checkout and marketing tools. It streamlines creator payouts and helps you grow your audience effortlessly. - [Instacart](https://composio.dev/toolkits/instacart) - Instacart is an online grocery delivery and pickup service platform. It lets you discover local retailers and create shoppable lists and recipes with ease. - [Junglescout](https://composio.dev/toolkits/junglescout) - Junglescout is an Amazon product research and analytics platform for sellers. It delivers sales estimates, competitive insights, and optimization tools to boost your Amazon business. - [Ko fi](https://composio.dev/toolkits/ko_fi) - Ko-fi is a platform that lets creators receive donations, memberships, and sales from fans. It helps creators monetize their work and grow their audience with minimal friction. - [Lemon squeezy](https://composio.dev/toolkits/lemon_squeezy) - Lemon Squeezy is a payments and subscription platform built for software companies. It makes managing payments, taxes, and customer subscriptions effortless. - [Loyverse](https://composio.dev/toolkits/loyverse) - Loyverse is a point-of-sale (POS) platform for small businesses, offering tools for sales, inventory, and customer loyalty. It helps streamline retail operations and boost customer engagement. - [Memberstack](https://composio.dev/toolkits/memberstack) - Memberstack lets you add user authentication, payments, and member management to your website—no backend code required. Easily manage your site's members and subscriptions from a single platform. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Countdown api MCP? With a standalone Countdown api MCP server, the agents and LLMs can only access a fixed set of Countdown api tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Countdown api 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 Countdown api tools. ### Can I manage the permissions and scopes for Countdown api while using Tool Router? Yes, absolutely. You can configure which Countdown api 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 Countdown api data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)