Bring Microblogging
to CrewAI
Learn how to connect Bluesky Social to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Bluesky Social MCP Server?
Connect your Bluesky account to any AI agent and take full control of your decentralized social interactions and automated microblogging workflows through natural conversation.
What you can do
- Microblogging Orchestration — Publish high-fidelity posts to your Bluesky profile programmatically with automatic link and mention detection in real-time
- Relationship Intelligence — Manage your social graph by following/unfollowing accounts and retrieving detailed high-fidelity follower/following directories
- Search & Profile Discovery — Access complete profile metadata, bios, and statistics for any handle or DID to coordinate your organizational social research
- Timeline & Feed Monitoring — Monitor your home timeline and notifications programmatically to maintain high-fidelity oversight of your social engagement
- Moderation Architecture — Programmatically mute or unmute actors and discover trending custom feed generators to perfectly coordinate your digital feed experience
How it works
1. Subscribe to this server
2. Retrieve your Handle (e.g., name.bsky.social) and generate an App Password in Bluesky settings (Settings > App Passwords)
3. Start orchestrating your decentralized social presence from Claude, Cursor, or any MCP client
No more manual toggling between social apps or missing important mentions in the feed. Your AI acts as your dedicated social media manager and AT Protocol architect.
Who is this for?
- Social Media Managers — instantly publish updates and monitor community feedback using natural language commands
- Developers & Power Users — automate the management of decentralized social connections without leaving your workspace
- Researchers — analyze trending feeds and search for influence patterns through simple AI queries
Built-in capabilities (12)
Post to Bluesky
Follow an account
Get user profile
List user posts
List account followers
List muted users
Get notifications
List popular feed generators
Get your home feed
Mute an account
Search for users
Unmute an account
Why CrewAI?
When paired with CrewAI, Bluesky Social becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Bluesky Social 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
Bluesky Social in CrewAI
Bluesky Social and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Bluesky Social 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 Bluesky Social in CrewAI
The Bluesky Social 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 12 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
Bluesky Social for CrewAI
Every tool call from CrewAI to the Bluesky Social MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Bluesky Handle and App Password?
Your handle is your username (e.g., name.bsky.social). For the password, go to Settings > App Passwords in Bluesky and generate a new one.
Can I search for users via AI?
Yes! The search_profiles tool allows your agent to find Bluesky users matching a text query programmatically.
How do I check my social notifications?
Use the list_notifications tool to retrieve recent likes, reposts, and mentions directly through your AI agent.
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.