Connect Emergency Communication Channel Plan to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Build reliable, tiered communication protocols for household crises.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 4 capabilities

The complete Emergency Communication Plan capability set.

These are the exact actions your AI can choose when you ask it to work with Emergency Communication Plan.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Emergency Communication Plan.

  1. 01

    Assign contact responsibilities

    This capability maps specific household members or backup contacts to communication tasks. It ensures every person knows exactly what they are responsible for monitoring during an event.

  2. 02

    Create testing schedule

    This capability generates a timeline for validating your communication plan. It helps you run regular drills to confirm your protocols are still effective.

  3. 03

    Generate message templates

    This capability creates concise, actionable message templates for emergency events. It ensures your alerts are brief and clear when you need to send them quickly.

  4. 04

    Get channel map

    This capability determines the best sequence of communication channels to use. It helps you establish a primary, secondary, and tertiary hierarchy for maximum reachability.

One connector, every AI

Emergency Communication Plan works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Emergency Communication Plan to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1238ms average. Fast in production.

Emergency Communication Plan is checked daily against the live service.

Daily averagePeak 1238ms
Sep 26Today
Fastest day
1238ms
Slowest day
1238ms
14-day trend
Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Emergency Communication Plan, so you can see the experience inside your AI.

It does not authenticate your account with Emergency Communication Plan. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Emergency Communication Plan Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_sUGXaExpjrBmYWePNlhZ4oPOM7QAuhlpscJJgWks/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Emergency Communication Plan capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "emergency-communication-channel-plan-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_sUGXaExpjrBmYWePNlhZ4oPOM7QAuhlpscJJgWks/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to Emergency Communication Plan

See all the AI clients this connector works with ↑

Who it's for

Built for the work Emergency Communication Plan owners hand off.

This MCP is for anyone responsible for the safety and coordination of a household or small group during emergencies.

  • 01

    Heads of Household

    They hand off the organization of contact hierarchies and task assignments to the AI.

  • 02

    Safety Coordinators

    They use the capability to generate testing schedules and message templates for group readiness.

  • 03

    Emergency Preparedness Planners

    They leverage the tiered mapping to ensure redundant communication paths are established.

FAQ

Questions Emergency Communication Plan owners ask.

  • 01

    What does this MCP actually do?

    It automates the creation of structured emergency communication protocols, including channel hierarchies, contact roles, and message templates.

  • 02

    How do I use this with Claude or Cursor?

    You connect your client to Vinkius, which hosts the MCP. Once connected, you can simply ask your AI client to perform tasks like mapping channels or assigning roles.

  • 03

    Can I use this for professional safety teams?

    Yes, it is designed to manage tiered communication hierarchies and task assignments for any group, including households or small teams.

  • 04

    How does the tiered hierarchy work?

    The MCP organizes communication into Primary, Secondary, and Tertiary layers to ensure you have backup methods if the first channel fails.

  • 05

    Do I need to host this myself?

    No, Vinkius hosts and manages the MCP for you. You just connect your client and start using the capabilities.

  • 06

    How does the channel hierarchy work?

    The system uses get_channel_map to organize channels into Primary, Secondary, and Tertiary tiers based on reliability and privacy constraints.

  • 07

    Can I assign specific roles to family members?

    Yes, you can use assign_contact_responsibilities to map contacts to specific household devices and define fallback contacts.

  • 08

    How do I ensure the plan is still working?

    You can generate a validation timeline using create_testing_schedule to ensure all communication channels remain functional.

Connect Emergency Communication Plan to Claude, Cursor, ChatGPT & more