JetBrains

How to give JetBrains access to Local Event Planner

Set up in seconds, once. From then on, JetBrains gets things done for you: add one server entry, and Local Event Planner is live in your IDE.

Ask AI about this guide

Local Event Planner Connector

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

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

Connecting Local Event Planner to JetBrains

About a minute, in Settings

  1. 1Go to Settings, Tools, AI Assistant, Model Context Protocol (MCP).
  2. 2Click Add and add Local Event Planner with the url field set to your link. The link above is the URL.
  3. 3Click OK and Apply, check the Status column, and ask something real. Local Event Planner is now part of your IDE.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "local-event-attendance-planner-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_rVlXoZ2chpWJ8yRDT6e0R7lOjJOhr25vH2tHUMeb/mcp"
    }
  }
}

JetBrains + Local Event Planner

One chat. Your Local Event Planner, live inside JetBrains.

Real prompts, answered with live data. This is the kind of session you will have in JetBrains once the server is in.

Waiting for input…

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

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

These prompts ship with the Local Event Planner Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the Local Event Planner Connector page.

Mission Control

See everything your JetBrains agents do in Local Event Planner.

When JetBrains runs a tool in Local Event Planner, it happens in your editor: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing
Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests
0
Total in this period
Avg Latency
0
API 88ms · Overhead 54ms
Vinkius Reliability
0
Agent 280 · Upstream 47 · Vinkius 15
Tokens
0
AI tokens processed
DLP Protected
0
Sensitive data redacted
Cost Saved
0
FinOps truncations applied

AI Agents Activities

last 30 days
30d agotoday

Request Volume & Latency

requests latency

Every request your JetBrains agents make through Local Event Planner is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Local Event Planner workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting Local Event Planner to your AI is step one. But an open line between your agents and Local Event Planner is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

01

Tamper Proof Activity Log

Every request your agents make in Local Event Planner is recorded and signed, so any change to the history becomes detectable.

02

Automatic Key Rotation

We rotate security keys every 24 hours. Your Local Event Planner connection stays protected without any manual work.

03

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Local Event Planner actions never surprise you.

04

Isolated Sandbox

Every execution through Local Event Planner runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

05

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so Local Event Planner activity lands in the tools you already rely on.

06

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your JetBrains sessions responsive.

07

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach Local Event Planner.

08

Credential Validation

We test your Local Event Planner credentials before saving them. Invalid credentials are rejected instead of being stored.

09

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every Local Event Planner connection runs on. Read how our infrastructure protects everything your JetBrains agents do, end to end.

Inside Vinkius

Get Local Event Planner ready for your AI. It's easy.

You choose Local Event Planner from the Vinkius Catalog and get one connection link. That's it.

  1. You choose Local Event Planner

    You find Local Event Planner in the Catalog and install the Connector with one click.

    Local Event Planner

    Active

    Enable Connector
    Activating…

  2. You add the link in JetBrains

    Vinkius gives you one connection link. In your JetBrains IDE, you add an MCP server in Settings with the link in the url field, and the connection is ready.

    Token generated successfully

    MCP Connection URL

    https://edge.vinkius.com/vk_preview_rVlXoZ2chpWJ8yRDT6e0R7lOjJOhr25vH2tHUMeb/mcp

    Connection Token

    vk_live_••••••••
    Go to Dashboard

Set it up once. Use Local Event Planner with the AI you already use.

FAQ

JetBrains access questions.

  • 01

    Which IDEs support this?

    The JetBrains AI Assistant: Settings, Tools, AI Assistant, Model Context Protocol (MCP), with global or project server level and the url field for remote servers.

  • 02

    If I connect Local Event Planner to JetBrains, can I use the same connection in Claude or ChatGPT later?

    Yes, and that's the point: the connection is yours, not JetBrains's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Local Event Planner is already there.

  • 03

    Do I need to hand my Local Event Planner password to JetBrains?

    Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. JetBrains only ever sees the link, and you can remove it whenever you want.

  • 04

    What can I actually ask JetBrains to do with Local Event Planner?

    Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.

  • 05

    JetBrains doesn't show the Connector. What do I check?

    Check the Status column in the MCP settings and make sure the url was pasted exactly as copied, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

  • 06

    Can I remove the access later?

    Untick the server in the MCP settings (or remove it) and it's out of your IDE. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

  • More questions about Local Event Planner? The Connector page answers them. See everything the Local Event Planner Connector can do

About the Connector

What Local Event Planner adds to your AI.

Once you connect it, your AI gains 4 capabilities: the exact actions it can take in Local Event Planner when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the Local Event Planner Connector can do