sipp-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_sipp_scenarioA | Execute a SIPp scenario for SIP protocol testing. Can run as UAC (client) or UAS (server) with custom scenarios. |
| create_sipp_scenarioB | Create a custom SIPp XML scenario file for testing |
| get_sipp_statisticsB | Parse and display statistics from SIPp CSV output files |
| check_sipp_versionA | Check if SIPp is installed and display version information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of SIPp testing: version check, scenario creation, execution, and statistics parsing. No overlap in purpose.
All tools follow a consistent verb_noun pattern: check_sipp_version, create_sipp_scenario, get_sipp_statistics, run_sipp_scenario.
4 tools is well-scoped for a SIPp testing server, covering the core workflow without unnecessary bloat.
Covers the main operations: check, create, run, and analyze. Minor gaps like scenario deletion or listing, but the core testing loop is complete.