Compatible with every major AI agent and IDE
What is the GaggleAMP MCP Server?
Connect your GaggleAMP manager account to any AI agent and take full control of your employee advocacy and B2B social marketing workflows through natural conversation.
What you can do
- Activity Orchestration — List and manage social sharing tasks (LinkedIn, Twitter) and retrieve detailed engagement metrics programmatically
- Advocate CRM — Manage your complete directory of members and retrieve detailed profiles, including point balances and impact scores
- Gamification Control — Access global and Gaggle-specific leaderboards to identify top performers and monitor your program's social footprint
- Reward Automation — List redeemable items and process reward claims for members using their earned points directly through your agent
- Team Onboarding — Programmatically invite new advocates to your Gaggle and manage team structures to scale your social reach
How it works
- Subscribe to this server
- Retrieve your API Token from your GaggleAMP Manager Dashboard (Settings > Integrations)
- Start managing your employee advocacy program from Claude, Cursor, or any MCP client
No more manual status checking or complex activity creation through slow web dashboards. Your AI acts as your dedicated advocacy program manager.
Who is this for?
- Marketing Managers — instantly launch new sharing activities and track campaign reach using natural language
- Social Media Leads — monitor top advocate performance and identify content that resonates best with the team
- HR & Culture Teams — manage employee recognition and reward redemptions without leaving your workspace
Built-in capabilities (12)
Add new task for members
Get user profile
Get stats for activity
Check point balance
Get rankings
Invite to Gaggle
List available activities
List accessible Gaggles
List redeemable items
List all advocates
Get claimed rewards
Process reward claim
Why CrewAI?
When paired with CrewAI, GaggleAMP becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GaggleAMP 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
GaggleAMP in CrewAI
GaggleAMP and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect GaggleAMP 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 | 4,000+ 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 GaggleAMP in CrewAI
The GaggleAMP 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
GaggleAMP for CrewAI
Every tool call from CrewAI to the GaggleAMP 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 get an API token in GaggleAMP?
Log in to your Manager Dashboard, navigate to Settings > Integrations, and copy the API Token provided under the API Access section.
Can I check a member's point balance via AI?
Yes! Use the get_member_points tool with the specific member ID to retrieve their current points and overall program impact.
Does the integration support inviting new users?
Absolutely. The invite_new_advocate tool allows you to send email invitations to join your program by providing a name and email address.
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.
Explore More MCP Servers
View all →
Salsa Engage
12 toolsAutomate non-profit outreach via Salsa Engage — manage supporters, activities, and fundraising analytics with AI.

TED EU
6 toolsSearch EU public procurement tenders via TED — find contracts by country, sector, or value range from any AI agent.

UKG Pro Learning
4 toolsManage employee training, courses, and learning paths via UKG Pro Learning.

Cart.com (AmeriCommerce)
10 toolsE-commerce store orchestration via Cart.com — manage products, orders, and customers via AI.
