solace-admin-read-mcp
by solacese
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | HTTP bind address (http mode only). | 127.0.0.1 |
| HTTP_PORT | No | HTTP listen port (http mode only). | 3000 |
| TRANSPORT | No | Transport mode: 'stdio' or 'http'. | stdio |
| SOLACE_VPN | Yes | Default message VPN name. Required. | |
| MCP_API_KEY | No | Bearer token for HTTP auth (required for http mode, min 32 characters). | |
| SEMP_BASE_URL | Yes | Broker SEMP v2 URL (e.g., https://host:943/SEMP/v2). Required. | |
| SEMP_PASSWORD | Yes | SEMP management password. Required. | |
| SEMP_USERNAME | Yes | SEMP management username. Required. | |
| ALLOWED_ORIGINS | No | Comma-separated CORS origins (supports wildcards, optional). | |
| SOLACE_CLOUD_TOKEN | No | Event Portal API token (optional; omit to disable Event Portal tools). |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/solacese/solace-admin-read-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server