SD Elements MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SDE_HOST | Yes | Your SD Elements instance URL (e.g., https://your-sdelements-instance.com) | |
| SDE_API_KEY | Yes | Your SD Elements API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List all projects in SD Elements |
| get_projectC | Get detailed information about a specific project |
| create_projectC | Create a new project in SD Elements |
| update_projectC | Update an existing project |
| delete_projectC | Delete a project |
| list_applicationsC | List all applications in SD Elements |
| get_applicationC | Get detailed information about a specific application |
| create_applicationC | Create a new application in SD Elements |
| update_applicationC | Update an existing application |
| list_countermeasuresC | List countermeasures for a project |
| get_countermeasureB | Get detailed information about a specific countermeasure |
| update_countermeasureC | Update a countermeasure status or details |
| list_usersC | List all users in SD Elements |
| get_userC | Get detailed information about a specific user |
| get_current_userA | Get information about the currently authenticated user |
| list_business_unitsB | List all business units |
| get_business_unitC | Get detailed information about a specific business unit |
| api_requestC | Make a custom API request to any SD Elements endpoint |
| test_connectionB | Test the connection to SD Elements API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| project_summary | Generate a summary of projects in SD Elements |
| security_status | Get security status overview for applications and projects |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the SD Elements domain. The tools are well-organized around entities like applications, projects, countermeasures, business units, and users, with clear CRUD operations that prevent confusion. No overlapping functionality exists that would cause misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_application, list_projects, get_user, and update_countermeasure. This predictable naming convention makes it easy for agents to understand and use the tools without ambiguity or mixed styles.
With 19 tools, the count is slightly high but reasonable for a comprehensive SD Elements API server covering multiple entities. It includes core operations for applications, projects, countermeasures, business units, and users, plus utility tools like test_connection and api_request, which justifies the scope without being excessive.
The tool set provides complete CRUD/lifecycle coverage for the SD Elements domain, including create, get, update, list, and delete operations for key resources. It also covers authentication (get_current_user), connection testing, and a flexible api_request tool, leaving no obvious gaps for agent workflows.