SRP Hub MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUB_API_BASE | No | Base URL of the Hub API | http://localhost:3001/v2 |
| HUB_API_TOKEN | Yes | Bearer token for Hub API auth |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_customerC | Cria um novo cliente (lead) no Hub. Use esta ferramenta para registrar leads encontrados em outras fontes. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as creating a new customer/lead in the hub, leaving no room for confusion or misselection.
The single tool follows a clear verb_noun pattern (post_customer), and with no other tools to compare against, there is no inconsistency in naming conventions. The naming is straightforward and predictable.
One tool is too few for a server named 'SRP Hub MCP', which implies a broader hub functionality. This minimal toolset feels thin and inadequate for typical hub operations like managing, updating, or retrieving customer data, limiting its usefulness.
The tool surface is severely incomplete for a hub domain. While it allows creating customers, there are significant gaps: no tools for reading, updating, deleting, or searching customers, which are essential for basic CRUD operations and will likely cause agent failures in handling customer data.