4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
GetStream MCP Server

Bring Activity Feeds
to CrewAI

Learn how to connect GetStream to CrewAI and start using 23 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Activity To FeedAdd To CollectionBatch Delete CollectionsBatch FollowBatch Get CollectionsBatch Post CollectionsDelete Collection ObjectDelete FileFollow FeedGet ActivitiesGet Collection ObjectGet FeedGet Open GraphList Feed FollowersList Feed FollowsPartial Update ActivityProcess ImageRemove Activity From FeedUnfollow FeedUpdate ActivitiesUpdate Collection ObjectUpload FileUpload Image

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
GetStream

What is the GetStream MCP Server?

Connect GetStream to your AI agent to orchestrate complex social architectures and activity feeds using natural language.

What you can do

  • Feed Management — Retrieve, add, or remove activities from specific feed slugs and user timelines using get_feed and add_activity_to_feed.
  • Activity Orchestration — Update activity metadata or perform partial updates to specific fields via partial_update_activity without rewriting entire objects.
  • Social Graph — Manage follower relationships, list who follows a feed, and perform follow operations using follow_feed and list_feed_followers.
  • Collections & Files — Handle collection objects and manage file/image uploads for rich media experiences.
  • Open Graph — Retrieve Open Graph data for URLs to enrich activity content automatically.

How it works

  1. Subscribe to this server
  2. Enter your Stream API Key and JWT Token
  3. Start managing your social infrastructure from any MCP-compatible client

Who is this for?

  • Product Managers — monitor feed health and activity patterns without technical dashboards.
  • Developers — test feed logic and activity updates directly from the IDE to speed up social feature integration.
  • Community Managers — manage social graphs and moderate feed content through natural conversation.

Built-in capabilities (23)

add_activity_to_feed

Add an activity to a feed

add_to_collection

Add objects to a collection

batch_delete_collections

Batch delete collections

batch_follow

Batch follow multiple feeds

batch_get_collections

Batch retrieve collections

batch_post_collections

Batch create/update collections

delete_collection_object

Delete an individual collection object

delete_file

Delete a file by URL

follow_feed

Follow a target feed

get_activities

Retrieve specific activities by ID or foreign ID

get_collection_object

Retrieve an individual collection object

get_feed

Supports pagination. Retrieve activities in a feed

get_open_graph

Scrape Open Graph data from a URL

list_feed_followers

List feeds following this feed

list_feed_follows

List feeds this feed follows

partial_update_activity

Partially update activity data

process_image

Process or resize an image

remove_activity_from_feed

Remove an activity from a feed

unfollow_feed

Unfollow a target feed

update_activities

Update activity metadata

update_collection_object

Update an individual collection object

upload_file

Upload a file

upload_image

Upload an image

Why CrewAI?

When paired with CrewAI, GetStream becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GetStream 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 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

See it in action

GetStream in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

GetStream and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect GetStream 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for GetStream in CrewAI

The GetStream 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 23 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.

GetStream
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

The Vinkius Advantage

How Vinkius secures GetStream for CrewAI

Every tool call from CrewAI to the GetStream MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I retrieve specific activities using their unique identifiers?

Yes. Use the get_activities tool by providing a comma-separated list of activity IDs or foreign IDs to fetch their full metadata.

02

How do I check which feeds a specific user is currently following?

You can use the list_feed_follows tool. Provide the feed slug and user ID to get a comprehensive list of all target feeds being followed.

03

Is it possible to update only a single field in an activity without sending the whole object?

Absolutely. The partial_update_activity tool allows you to set or unset specific fields on an activity using a JSON payload, preserving the rest of the data.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →