Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@perfsonar-mcpCheck the packet loss between host-a and host-b over the last 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
perfsonar-mcp
MCP (Model Context Protocol) server for perfSONAR - Query measurements, discover testpoints, and schedule network tests.
π Features
Measurement Archive Queries
Query historical measurements with filters
Get throughput, latency, and packet loss data
Access raw time-series data with summaries
Discover available measurement types
Lookup Service Integration
Find perfSONAR testpoints globally
Search by location (city, country)
Locate pScheduler services for testing
Test Scheduling (pScheduler)
Schedule throughput tests (iperf3)
Schedule latency tests (owping)
Schedule RTT tests (ping)
Monitor test status and retrieve results
π¦ Installation
For development with additional tools:
βοΈ Configuration
Required environment variable:
Optional:
π Usage
Local
Docker
Kubernetes
π€ Claude Desktop Integration
Add to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
π§ Available Tools (13)
Measurement Archive (6)
query_measurements- Search measurementsget_throughput- Throughput dataget_latency- Latency dataget_packet_loss- Packet loss dataget_measurement_data- Raw time-seriesget_available_event_types- List types
Lookup Service (2)
lookup_testpoints- Find testpointsfind_pscheduler_services- Find pScheduler
pScheduler (5)
schedule_throughput_test- Run throughput testschedule_latency_test- Run latency testschedule_rtt_test- Run RTT testget_test_status- Check statusget_test_result- Get results
π‘ Example Queries
Ask Claude:
"Find perfSONAR testpoints in Europe"
"Schedule a 30-second throughput test to host.example.com"
"Get hourly throughput averages between host1 and host2 for the last week"
ποΈ Architecture
π οΈ Development
Logging
The server includes comprehensive logging for development and debugging. By default, logs are written to stderr at INFO level.
To enable DEBUG logging for more detailed output:
Or set the log level via environment variable:
Log output includes:
Server initialization and configuration
API requests and responses
Tool invocations with arguments
Error details with stack traces
DevContainer
Open in VS Code β Reopen in Container
Local Development
π Documentation
π Resources
π License
MIT