Cursor Mcp Collector
What is Cursor Mcp Collector
cursor-mcp-collector is a script designed to automate the collection and processing of Cursor’s mcp.json configuration files from multiple workspaces. It can either package these files into a zip archive or send them directly to a Splunk HTTP Event Collector (HEC).
Use cases
Use cases for cursor-mcp-collector include automating the collection of configuration files for backup purposes, integrating with Splunk for real-time monitoring and analysis, and simplifying the management of multiple workspaces’ configurations.
How to use
To use cursor-mcp-collector, you need to configure the script by editing the Splunk settings at the top. You can choose between two operation modes: Zip collection mode (by setting SPLUNK_ENABLED to false) or Splunk integration mode (by setting SPLUNK_ENABLED to true). Run the script in a Bash shell with the necessary prerequisites installed.
Key features
Key features include automatic discovery of all Cursor workspaces, collection of both global and workspace-specific mcp.json files, and two operational modes: Zip collection and Splunk integration.
Where to use
cursor-mcp-collector is primarily used in environments where Cursor’s mcp.json files are utilized, particularly in data processing and monitoring setups that integrate with Splunk for log management and analysis.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Cursor Mcp Collector
cursor-mcp-collector is a script designed to automate the collection and processing of Cursor’s mcp.json configuration files from multiple workspaces. It can either package these files into a zip archive or send them directly to a Splunk HTTP Event Collector (HEC).
Use cases
Use cases for cursor-mcp-collector include automating the collection of configuration files for backup purposes, integrating with Splunk for real-time monitoring and analysis, and simplifying the management of multiple workspaces’ configurations.
How to use
To use cursor-mcp-collector, you need to configure the script by editing the Splunk settings at the top. You can choose between two operation modes: Zip collection mode (by setting SPLUNK_ENABLED to false) or Splunk integration mode (by setting SPLUNK_ENABLED to true). Run the script in a Bash shell with the necessary prerequisites installed.
Key features
Key features include automatic discovery of all Cursor workspaces, collection of both global and workspace-specific mcp.json files, and two operational modes: Zip collection and Splunk integration.
Where to use
cursor-mcp-collector is primarily used in environments where Cursor’s mcp.json files are utilized, particularly in data processing and monitoring setups that integrate with Splunk for log management and analysis.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
Cursor MCP Collector
A script to automatically collect and process Cursor’s mcp.json configuration files from all workspaces. The script can either package the files into a zip archive or send them directly to a Splunk HTTP Event Collector (HEC).
Features
- Automatically discovers all Cursor workspaces
- Collects both global and workspace-specific
mcp.jsonfiles - Two operation modes:
- Zip collection: Packages all found files into a zip archive
- Splunk integration: Sends files directly to Splunk HEC
Prerequisites
- Bash shell
curl(for Splunk integration)zip(for zip collection mode)
Configuration
Edit the following settings at the top of the script:
# Splunk settings
SPLUNK_ENABLED=true # Set to false to disable Splunk integration
SPLUNK_URL="https://hec.example.com:8088"
SPLUNK_TOKEN="your-auth-token"
SPLUNK_INDEX="your-index"
SPLUNK_SOURCETYPE="your-sourcetype"
Operation Modes
Zip Collection Mode
When SPLUNK_ENABLED=false:
- Creates a temporary directory
- Collects all
mcp.jsonfiles - Packages them into
/tmp/collected_mcp.zip - Cleans up temporary files
Splunk Integration Mode
When SPLUNK_ENABLED=true:
- Discovers all
mcp.jsonfiles - Sends each file directly to Splunk HEC
- Includes workspace information in the event data
- No temporary files or zip archive created
For more details about manual collection, see manual-collection.md.
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.
