3,400+ MCP servers ready to use
Vinkius

Bring Lms
to CrewAI

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

Freeze UserGet User DetailsInvite UserList Completed AssignmentsList GroupsList Overdue AssignmentsList UsersUnfreeze UserUpdate User

What is the Innform MCP Server?

Connect your Innform training portal to any AI agent and take full control of your Learning Management System (LMS) and employee compliance workflows through natural conversation.

What you can do

  • User Lifecycle Orchestration — List all learners and admins, retrieve detailed high-fidelity profile metadata, and invite new users programmatically
  • Assignment Intelligence — Programmatically monitor completed and overdue training assignments to maintain a perfectly coordinated compliance overview
  • Training Group Architecture — Access your complete directory of learner groups and their properties to oversee your organizational training structure
  • Access Control Management — Programmatically freeze or unfreeze learner accounts to manage platform access dynamically based on organizational needs
  • Operational Monitoring — Verify API connectivity and monitor training progress directly through your agent for instant performance reporting

How it works

1. Subscribe to this server
2. Retrieve your API Key from your Innform dashboard (Account Settings > Integrations)
3. Start orchestrating your training ecosystem from Claude, Cursor, or any MCP client

No more manual checking of individual progress bars or digging through CSV reports. Your AI acts as your dedicated training coordinator and compliance architect.

Who is this for?

  • L&D Managers — instantly retrieve training completion recaps and manage user access using natural language commands
  • Compliance Officers — monitor overdue assignments and verify team progress without leaving your workspace
  • HR Operations — automate the onboarding of new learners into specific groups through simple AI queries

Built-in capabilities (9)

freeze_user

Freeze a user account

get_user_details

Get details for a specific user

invite_user

Invite a new learner

list_completed_assignments

List completed training assignments

list_groups

List learner groups

list_overdue_assignments

List overdue training assignments

list_users

List Innform users

unfreeze_user

Unfreeze a user account

update_user

Update an existing user

Why CrewAI?

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

Innform in CrewAI

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

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

Teams that connect Innform 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 Innform in CrewAI

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

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

Every tool call from CrewAI to the Innform 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 Innform API Key?

Log in to your account, navigate to Account Settings > Integrations, and copy your unique API Key from the access section.

02

Can I freeze a user account via AI?

Yes! The freeze_user tool allows your agent to temporarily disable platform access for a specific learner programmatically.

03

How do I check for overdue assignments?

Use the list_overdue_assignments tool to retrieve a comprehensive list of all training items that have passed their high-fidelity deadlines.

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.