Skip to content

Splunk MCP connector

The Splunk connector brings Splunk users, roles, outbound ports and IP allowlists to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every call made as the signed-in person and recorded in an audit log.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List every Splunk role and who holds admin

Working in Splunk with Elaichi

  • List all Splunk users
  • Get single Splunk user by ID
  • List all Splunk roles
Ask anything…
Governance / Audit log Last 24 hours
Splunk List all Splunk roles Emily Carter · Claude · 9:41 AM Done
Splunk Get single Splunk user by ID Emily Carter · Claude · 9:41 AM Done
Splunk List all Splunk users Emily Carter · Claude · 9:41 AM Done
Splunk Create a Splunk user Megan Brooks · ChatGPT · 9:38 AM Done
Splunk Update a Splunk user by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Splunk to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Splunk MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Splunk MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Splunk MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Splunk MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Splunk MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Splunk to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Splunk through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Splunk is logged.

  • IT

    Set up a new engineer in Splunk

    Create the Splunk user from a chat, give them the right role, and confirm the account exists before their first day. No one has to open the admin console.

  • Security

    Review who holds the admin role

    Ask for every Splunk role and the users attached to it, then spot the people who still have more access than they need.

  • Platform

    Open an outbound port for a new destination

    Add the outbound port Splunk needs to reach a new forwarding target, list what is already open, and remove ports nobody uses any more.

  • Networking

    Add an office address to the allowlist

    When a site moves or a VPN changes, add the new IP allowlist entry in Splunk and clear the old ones in one go.

  • Compliance

    Pull the user and role list for an audit

    Get a current list of Splunk users and their roles as a plain summary you can hand to an auditor without exporting anything by hand.

  • Helpdesk

    Fix a user who cannot see their data

    Look up the Splunk user by name, check which role they hold, and update it so they can get back to work.

Try asking

  • “List every Splunk role and who holds admin”
  • “Create a Splunk user for the new SRE with the analyst role”
  • “Which IP allowlist entries are set in Splunk right now?”

See all 112 Splunk tools →

What connecting Splunk gets you

6 screens from Elaichi, each doing one job for your Splunk account.

Elaichi Agent

Ask Elaichi to work across your apps.

List every Splunk role and who holds admin

Create a Splunk user for the new SRE with the analyst role

Which IP allowlist entries are set in Splunk right now?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Splunk users in plain language.

Live answers on Splunk users, roles, ports and allowlists from one chat screen.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Splunk from any MCP client, one endpoint.

Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Splunk users List List Splunk Cloud users on the stack (GET /{stack}/adminconfig/v2/users, Admin Config Service). Returns name, email, fullName, roles, defaultApp, lockedOut, lastSuccessfulLogin. Paginated with count/offset (max 100 per page). Users are local to the search head the token was created on.
Get single Splunk user by ID Get Get one Splunk Cloud user (GET /{stack}/adminconfig/v2/users/{userName}). The id is the user name (login). Returns name, email, fullName, roles, capabilities, defaultApp, lockedOut, lastSuccessfulLogin.
Create a Splunk user Create Create a new user. Splunk Cloud Admin Config Service (POST /users). Required: name, password. The optional Federated-Search-Manage-Ack header (only needed when granting fsh_manage) is not sent.
Update a Splunk user by ID Update Modify a specific user on the stack. Splunk Cloud Admin Config Service (PATCH /users/{userName}). The id is the userName. Required: id. The optional Federated-Search-Manage-Ack header (only needed when granting fsh_manage) is not sent.
Delete a Splunk user by ID Delete Delete a specific user. Splunk Cloud Admin Config Service (DELETE /users/{userName}). The id is the userName. Required: id.

Tool catalog

112 Splunk tools, no code to write.

Users, roles, outbound ports and IP allowlists, every method ready the moment you connect.

ElaichiToolboxes
Name Source template Tools Created

IT toolbox

Splunk · users and onboarding

Splunk starter 18 Mar 4, 2026

Security toolbox

Splunk · roles and allowlists

— 9 Mar 2, 2026

Platform toolbox

Splunk · outbound ports

— 24 Feb 27, 2026

Networking toolbox

Splunk · IP allowlists

Splunk starter 6 Feb 19, 2026

Compliance toolbox

Splunk · user and role reviews

— 31 Jan 30, 2026

Helpdesk toolbox

Splunk · user lookups and fixes

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Splunk toolbox.

Security, IT and Platform each see only the Splunk tools scoped to them.

ElaichiConnections
Connection Scope Status Access
SP

Splunk (Production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SP

Splunk (Staging)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SP

Splunk (Security)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SP

Splunk (Platform)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
SP

Splunk (EMEA)

Connected by Ryan Hayes

Personal • Active Not shared
SP

Splunk (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share Splunk access without sharing the key.

One person connects Splunk and teammates work through it, never seeing the API key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Splunk Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Splunk Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Splunk Users List Toolbox

Audit log

Know who changed what in Splunk.

Every user, role and allowlist change is logged with who, when and which resource.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Splunk digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    Splunk

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Splunk

    Queued

Workflows

A schedule runs the Splunk access review.

Users are fetched, grouped by role, summarized, approved by a person, then updated in Splunk.

Splunk health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Roles

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Production 34%

Staging 27%

Security 21%

Platform 18%

Collections and dashboards

Splunk user counts, computed without a model.

Users created over 14 days, split by team, refreshed on a schedule, nobody has to ask.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Splunk

All three can connect Splunk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Splunk, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Splunk tools Allow or restrict single Splunk tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Splunk call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Splunk tools for your AI agents

112 tools are ready to call through Elaichi's MCP endpoint the moment you connect Splunk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Splunk to Claude?

Connect Splunk in Elaichi first by pasting a Splunk API key, which is the only sign-in step Splunk asks for. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Splunk is ready to use.

Does Splunk work with ChatGPT and Cursor as well as Claude?

Yes. Once Splunk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Splunk once and every client picks it up.

What can an AI agent actually do with my Splunk data?

With Splunk connected, an agent can list, create, update and delete Splunk users and roles, manage outbound ports, and add or remove IP allowlist entries. You can ask who holds the admin role, set up a new user with the right role, or add an office address to the allowlist. Short, concrete asks like "list Splunk roles" work better than long paragraphs.

Does connecting Splunk give the AI every user, role and setting?

No. Every call to Splunk runs as the person who signed in, so the agent can only reach the users, roles, ports and allowlists that person's own Splunk access permits. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

Can my team share one Splunk connection?

Yes. One person connects Splunk with an API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change in Splunk.

Can I stop an agent from deleting or changing things in Splunk?

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Splunk users or changing roles for a role or for one person while leaving listing and lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it whatever the prompt says.

What happens to a Splunk connection when someone leaves?

Offboarding a person in Elaichi ends their access to Splunk through every client at once. A shared Splunk connection keeps working for everyone else on the team. If you ever need to remove Splunk entirely, disconnecting it once in Elaichi removes it from every client.

Does the Splunk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Splunk is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Splunk?

Yes. Both let Claude, ChatGPT or Cursor use Splunk. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Splunk call.

How is Elaichi different from Composio for Splunk?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Splunk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Splunk in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot