Catalog adapters for a vendor's own MCP server; Splunk first - #830
Merged
Merged
Conversation
- Adapter type MCP: at install the tools come from the workspace's server (tools/list), so it gets exactly what its server version offers; the catalog's list is the snapshot shown in the store and the fallback when the server cannot be reached. Listing the tools is the install check. - Catalog policy on top: "enabled": false installs a tool switched off, catalog annotations override the server's; catalog updates never rewrite or retire an MCP adapter's tools - Splunk adapter over the official Splunk MCP Server app (16 tools, dashboard writes off by default), with setup for the encrypted MCP token, mcp_tool_execute and the port 8089 allow list - 266 adapters
…win over the catalog's - Satellite config + hand-written prompts, FAQ, auth and troubleshooting; topics measured; optional title so the repo is not named like Splunk's own product - The catalog snapshot carries Splunk's annotations again (read/write in the store and the satellite); at install the server's hints win and the catalog only fills what the server leaves out (the dashboard tools) - Satellite READMEs: drop the header row of hand-written troubleshooting tables whatever it is called (Jev showed a stray 'Symptom' row)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some vendors now ship an official MCP server. Describing their API again in a REST adapter duplicates what they maintain; bridging their server is better, and what AnythingMCP adds on top (OAuth for Claude/ChatGPT, per-tool roles, audit, response mapping, other systems behind the same endpoint) is the value. First case: a Cisco user bridged the official Splunk MCP Server on 2 Oct and it worked end to end from Claude Desktop.
MCP adapters
connector.type: "MCP"in the catalog. At install the tools come from the workspace's server (tools/list), so it gets exactly the tools of its server version. The adapter'stoolsarray is a snapshot: shown in the store, installed as a fallback when the server cannot be reached, and the place for policy."enabled": falseinstalls a tool switched off (also honoured for REST adapters); catalog annotations fill the hints the server leaves out (the server's own hints win).ConnectorsService.discoverRemoteMcpTools()with env interpolation and the placeholder guard.Splunk adapter (
intl/splunk.json)https://{{SPLUNK_HOST}}:8089/services/mcp, Bearer with the encrypted MCP token.splunk_run_query/splunk_run_saved_searchas able to write (SPLcollect/outputlookup/delete), so the instructions say to use a read-only role.mcp_tool_execute, and the Splunk Cloud allow list for port 8089.Tests:
mcp-adapter.spec.ts(merge policy, install with the server reachable and with a 403 falling back to the snapshot), catalog re-sync for MCP adapters, catalog shape rule for MCP mappings. Adapters + connectors suites pass locally (HANA spec needs the optionalhdbmodule).Satellite
keysersoft/splunk-mcp-gateway(config, prompts, FAQ, auth, troubleshooting, measured topics; not published yet). Satellite generator: optionaltitle(so the repo is not named like Splunk's own "Splunk MCP Server"), and hand-written troubleshooting tables lose their header row whatever it is called (Jev's README showed a stray "Symptom" row).Counts: 266 adapters. Docs:
docs/tool-definition.mdhas an "MCP adapters" section.