How do I get a Poe API access token?

Go to [creator.poe.com](https://creator.poe.com/), navigate to Settings > API, and generate an access token. This token authenticates all API requests for bot management.

What AI models can I query through Poe?

Poe has GPT-4, GPT-4o, Claude 3.5 Sonnet, Claude 3 Opus, Llama 3, and dozens of specialized bots. Use query_bot to chain responses from multiple models in your workflows.

How does bot chaining work?

Using Poe API v2, your bot can query any other bot on Poe for free. The response becomes input for your bot's processing. Costs are covered by the user's free message limit or subscription.

Poe MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Poe
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Poe through the Vinkius — pass the Edge URL in the `mcps` parameter and every Poe tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Poe Specialist",
    goal="Help users interact with Poe effectively",
    backstory=(
        "You are an expert at leveraging Poe tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Poe "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Poe MCP Server

Connect your Poe (Quora's AI platform) account to any AI agent and manage your chatbot empire through natural conversation. Create bots, chain AI model responses, monitor conversations, and track performance — all via API.

When paired with CrewAI, Poe becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Poe tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Bot Management — List, create, update, and delete API bots programmatically
AI Model Chaining — Query any bot on Poe (GPT-4, Claude, etc.) from your bot using API v2
Message Monitoring — View recent conversations, debug responses, and analyze user interactions
Usage Statistics — Track message counts, unique users, response times, and error rates
Endpoint Testing — Send test messages to verify bot connectivity and response quality
Multi-Model Workflows — Build complex bots that combine responses from multiple AI models

The Poe MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Poe to CrewAI via MCP

Follow these steps to integrate the Poe MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Poe

Why Use CrewAI with the Poe MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Poe through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Poe + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Poe MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Poe for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Poe, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Poe tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Poe against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Poe MCP Tools for CrewAI (10)

These 10 tools become available when you connect Poe to CrewAI via MCP:

create_bot

Requires a bot name, base URL for your API endpoint, and the model name. Optionally set a system prompt and description. Create a new API bot on Poe

delete_bot

This action cannot be undone. All conversation history and settings for the bot will be lost. Delete a Poe API bot

get_bot

Use the bot ID obtained from list_bots. Get details of a specific Poe bot

get_bot_stats

Essential for monitoring bot health, understanding user engagement, and identifying performance bottlenecks. Get usage statistics for a Poe bot

list_available_bots

Useful for discovering which AI models and specialized bots are available for chaining in your bot workflows. List publicly available bots on Poe that your bot can query

list_bots

Returns bot names, handles, models, and status. Essential first step to identify which bot to work with before querying, updating, or checking stats. List all API bots under your Poe account

list_messages

Useful for monitoring what users are asking, debugging bot responses, and analyzing conversation patterns. Returns message content, timestamps, and user identifiers. List recent messages for a specific Poe bot

query_bot

This allows chaining bot responses - your bot can query GPT-4, Claude, or any other bot on Poe and use the response as input. The cost is covered by the user's free message limit or subscription. Query another bot on Poe from your bot

send_message

Useful for testing endpoint connectivity and validating bot responses. The bot will process the message and return a response via its configured endpoint. Send a message to a Poe bot (simulate user interaction)

update_bot

Changes take effect immediately for new conversations. Update an existing Poe bot's configuration

Example Prompts for Poe in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Poe immediately.

"List all my bots and show stats for the first one."

"Create a bot called 'Research Assistant' using GPT-4 that summarizes articles."

"Query Claude-3.5-Sonnet from my ResearchBot: 'What are the key trends in AI?'"

Troubleshooting Poe MCP Server with CrewAI

Common issues when connecting Poe to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Poe + CrewAI FAQ

Common questions about integrating Poe MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.