MCP Server: Weather & Upnify Integration
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-upnify-prospectC | Create a new prospect in Upnify CRM |
| get-upnify-sales-reportC | Get sales report from Upnify with customizable grouping, period, year and tax options |
| get-upnify-pending-paymentsB | Get pending payments report from Upnify with customizable grouping and period options |
| create-upnify-reminderB | Create a new reminder in Upnify agenda |
| search-upnify-contactsB | Search for contacts (prospects and clients) in Upnify by name, email, or phone |
| create-upnify-opportunityB | Create a new opportunity for a prospect in Upnify CRM (requires tkProspecto from search) |
| get-upnify-activity-reportC | Get activity report from Upnify by group or executive and period |
| get-upnify-conversion-reportC | Get conversion report from Upnify by group, executive, origin, or region and period |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: three create operations for different Upnify entities (opportunity, prospect, reminder), four get operations for different report types (activity, conversion, pending payments, sales), and one search tool for contacts. The descriptions specify unique targets and parameters, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with 'create-' or 'get-' or 'search-' prefixes, all using kebab-case (e.g., create-upnify-opportunity, get-upnify-sales-report). This uniformity makes the set predictable and easy to parse for an agent.
With 8 tools, the count is reasonable for the server's purpose of integrating weather and Upnify CRM operations. It's slightly under the typical 3-15 range but covers core Upnify functions well; however, the weather aspect is not represented in the tool names, suggesting a potential scope mismatch.
For Upnify CRM operations, the tools provide good coverage for creating prospects, opportunities, and reminders, and retrieving various reports and contacts. However, there are notable gaps: no update or delete operations for entities, no weather-related tools as implied by the server name, and no direct integration between weather and Upnify functions, which limits workflow completeness.