How do I get my Applied Epic API credentials?

Register your application in the [Applied Dev Center](https://developer.myappliedproducts.com/) to receive a Client ID and Client Secret. You will also need your Enterprise ID and Epic Database Name.

What is the Database Name?

The Database Name is the internal name of your Applied Epic database. You can find this information in your Epic platform settings or by contacting your agency's system administrator.

Can I see document attachments?

Yes, the `list_attachments` tool allows you to find documents and files linked to clients and policies, though the content itself remains secured in your Epic platform.

Applied Epic MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Applied Epic
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Applied Epic through Vinkius, pass the Edge URL in the `mcps` parameter and every Applied Epic tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Applied Epic Specialist",
    goal="Help users interact with Applied Epic effectively",
    backstory=(
        "You are an expert at leveraging Applied Epic tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Applied Epic "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About Applied Epic MCP Server

The Applied Epic MCP Server provides a powerful natural language interface to your Applied Systems insurance management platform. Connect your Applied Epic account to your AI agent to gain real-time visibility into your client relationships, policy lifecycles, and agency workflows.

When paired with CrewAI, Applied Epic becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Applied Epic tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Key Capabilities

Client Management — List and search for clients, and access full demographic and compliance data.
Policy Lifecycle — Track active and historical policies, including effective and expiration dates and current statuses.
Workflow Automation — Create and manage activities (tasks/logs) directly from your chat interface to ensure consistent follow-ups.
Lines of Business — Drill down into specific lines of business for any policy, such as Workers Comp or General Liability.
Attachment Oversight — Find and manage documents, photos, and proof of insurance linked to your clients and policies.
Secure Integration — Uses industry-standard OAuth 2.0 authentication to safely access your agency's data.

The Applied Epic MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Applied Epic to CrewAI via MCP

Follow these steps to integrate the Applied Epic MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from Applied Epic

Why Use CrewAI with the Applied Epic MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Applied Epic through the Model Context Protocol.

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

Applied Epic + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Applied Epic MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Applied Epic for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Applied Epic, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Applied Epic tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Applied Epic against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Applied Epic MCP Tools for CrewAI (9)

These 9 tools become available when you connect Applied Epic to CrewAI via MCP:

create_activity

Create a new activity record

get_account_check

Verify Applied Epic account connection

get_client

Get details for a specific client

get_policy

Get details for a specific policy

list_activities

List all activities (tasks/logs)

list_attachments

List all file attachments

list_clients

List all insurance clients in Applied Epic

list_lines

g., Workers Comp, GL) for a specific policyId. List lines of business for a policy

list_policies

List all insurance policies

Example Prompts for Applied Epic in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Applied Epic immediately.

"List all active insurance clients."

"Show me upcoming policy expirations for next month."

"Create an activity 'Renewal Follow-up' for client ID 'C998877'."

Troubleshooting Applied Epic MCP Server with CrewAI

Common issues when connecting Applied Epic to CrewAI through the Vinkius, and how to resolve them.

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.

Applied Epic + CrewAI FAQ

Common questions about integrating Applied Epic MCP Server with CrewAI.

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.