3,400+ MCP servers ready to use
Vinkius

Bring Edapp
to CrewAI

Learn how to connect EdApp 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.

Create New LearnerGet Account InfoGet Catalog StatisticsGet Course Progress ReportGet Learner DetailsGet Lesson Attempts LogList Active WebhooksList Course CollectionsList Course LessonsList LearnersList Training CoursesRemove Learner

What is the EdApp MCP Server?

Connect your EdApp (now SC Training) account to any AI agent and take full control of your corporate training and mobile learning workflows through natural conversation.

What you can do

  • Learner Orchestration — List and manage your learning community programmatically, including registering new users and retrieving detailed learner profiles
  • Catalog Intelligence — Access your complete course catalog and retrieve metadata for lessons and course collections to coordinate training content
  • Success Monitoring — Programmatically track course progress and retrieve high-fidelity analytics on completion rates and student engagement
  • Interaction Insight — Access detailed logs of lesson attempts and user activity to identify knowledge gaps and coordinate coaching
  • Operational Visibility — Check active webhooks and retrieve account metadata directly through your agent for instant L&D reporting

How it works

1. Subscribe to this server
2. Retrieve your API Token from the EdApp/SC Training Admin Portal (Settings > API)
3. Start managing your workforce development from Claude, Cursor, or any MCP client

No more manual status checking or digging through student lists in the portal. Your AI acts as your dedicated learning and development coordinator.

Who is this for?

  • HR & L&D Managers — instantly retrieve training completion reports and onboard new hires using natural language commands
  • Corporate Trainers — monitor individual learner progress and identify lessons with high failure rates without leaving your workspace
  • Operations Leads — automate user provisioning and training assignments through simple AI queries

Built-in capabilities (12)

create_new_learner

Add learner to EdApp

get_account_info

Get admin info

get_catalog_statistics

Check training stats

get_course_progress_report

Check learner progress

get_learner_details

Get user profile

get_lesson_attempts_log

Check lesson interactions

list_active_webhooks

Get event notifications

list_course_collections

List grouped content

list_course_lessons

List course content

list_learners

List EdApp users

list_training_courses

List all courses

remove_learner

Delete learner

Why CrewAI?

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

EdApp in CrewAI

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

EdApp and 3,400+ other MCP servers. One platform. One governance layer.

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

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ 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 EdApp in CrewAI

The EdApp 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.

EdApp
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 EdApp for CrewAI

Every tool call from CrewAI to the EdApp 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

How do I find my API Token?

Log in to the Admin Portal, navigate to Settings > API, and generate a new Access Token for your integration.

02

Can I filter progress by specific courses?

Yes! The get_course_progress_report tool allows you to specify a courseId to retrieve analytics for a particular training program.

03

Does it support adding new learners programmatically?

Absolutely. Use the create_new_learner tool with an email address to register a new user for your training platform.

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.