All Apps and Add-ons

Can't make Splunk native MCP Server work with N8N MCP Client

xvalette
Engager

Hello Splunk Community 🙂,

I am trying to use the following MCP Server : https://splunkbase.splunk.com/app/7931 on my Splunk On-Prem Docker deployment,

The application is installed successfully, the token was created for the admin role, and connectivity is ok between the MCP Client and the MCP Server :

xvalette@XVALETTE-M-06WY ~ % curl -X GET "https://splunk-xvalette.com/services/mcp" \
-H "Authorization: Bearer MY_ADMIN_TOKEN"

{"message":"Method not allowed"}

 However, I am getting an error "Could not connect to your MCP server" on the N8N MCP Client :

xvalette_0-1758799386680.png

I am able to connect to other MCP Servers, so the N8N configuration seems okay,

Is there any step that I am missing to make this work ?

Thanks for your help,

Xavier

Labels (1)
Tags (3)
0 Karma
1 Solution

xvalette
Engager

I just fix my situation,

The audience should be "mcp",

I saw this while checking the code :

xvalette_0-1758984379924.png

Hope it will help !

 

View solution in original post

Cloud001
Explorer

Thank you for your reply.

0 Karma

Cloud001
Explorer

This is not an answer to the question.
I am also testing the APP, but I’m reaching out because the connection is not working.

- Instead of using cmd, were you able to connect when querying through an MCP Host (e.g., Claude, Cursor, etc.)?

0 Karma

xvalette
Engager

Neither Claude or N8N MCP Client is able to connect to the MCP server,

I am not an MCP expert, but the logging is pretty light on my end..

The logs on Claude : 

2025-09-26T17:21:24.987Z [info] [splunk-mcp-server] Server started and connected successfully

2025-09-26T17:21:25.027Z [info] [splunk-mcp-server] Message from client: {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}

2025-09-26T17:21:26.070Z [info] [splunk-mcp-server] Server transport closed

2025-09-26T17:21:26.070Z [info] [splunk-mcp-server] Client transport closed

2025-09-26T17:21:26.070Z [info] [splunk-mcp-server] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.

2025-09-26T17:21:26.070Z [error] [splunk-mcp-server] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging)

2025-09-26T17:21:26.070Z [info] [splunk-mcp-server] Client transport closed
0 Karma

xvalette
Engager

I just fix my situation,

The audience should be "mcp",

I saw this while checking the code :

xvalette_0-1758984379924.png

Hope it will help !

 

Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...