Bring Content Scheduling
to CrewAI
Learn how to connect Typefully to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Typefully MCP Server?
Connect your Typefully account to any AI agent and simplify how you draft, schedule, and publish high-engagement content for X (Twitter) and LinkedIn through natural conversation.
What you can do
- Draft Management — List all your content drafts and retrieve detailed text and settings for specific ideas.
- Instant Publishing — Post content immediately to all your enabled social platforms directly via AI commands.
- Smart Scheduling — Schedule your posts for a specific time or use the 'next-free-slot' feature to optimize your queue.
- Account Directory — List all connected social sets and brands managed in your Typefully workspace.
- Draft Lifecycle — Create, update, and delete drafts programmatically to maintain your content pipeline.
- User Insights — Retrieve your profile details and verify account configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Typefully Personal API Key (found in your settings under API)
3. Start managing your social presence from Claude, Cursor, or any MCP client
Who is this for?
- Content Creators & Influencers — quickly draft threads and schedule posts via simple AI commands.
- Marketing Managers — monitor content queues and publish updates across multiple brands directly from the workspace.
- Social Media Teams — coordinate draft reviews and optimize publishing times via the AI assistant.
Built-in capabilities (9)
Create a new content draft
Remove a draft
Get details for a draft
Get your Typefully profile
List content drafts
List connected social accounts
Publish content right now
Schedule content for later
Modify an existing draft
Why CrewAI?
When paired with CrewAI, Typefully becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Typefully tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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 Vinkius Edge URL directly in the
mcpsparameter 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
Typefully in CrewAI
Typefully and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Typefully to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Typefully in CrewAI
The Typefully 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. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Typefully for CrewAI
Every tool call from CrewAI to the Typefully MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I publish to both X and LinkedIn at the same time?
Yes! When using the publish_immediately tool, you can specify the target platform or let Typefully post to all enabled channels for that social set.
How do I schedule a post for the next available time slot?
Use the schedule_content tool and set the publishAt parameter to 'next-free-slot'. Typefully will automatically place the post in the best upcoming time according to your queue settings.
Is it possible to see the content of an existing draft?
Absolutely. Use the get_draft_details tool and provide the Social Set ID and Draft ID. The agent will retrieve the full text and configuration for that draft.
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.
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
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.