Nexxupp MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Set to 'hosted' to enable hosted mode. Default is local stdio mode. | |
| MCP_PORT | No | Port for HTTP transport. Default is 3100. | |
| LOG_LEVEL | No | Log level: debug, info, warn, or error. Default is info. | |
| MCP_TRANSPORT | No | Transport to use: 'stdio' (default) or 'http'. | |
| NEXXUPP_EMAIL | No | Your Nexxupp login email. Required for NWS + Calendar tools in local mode. | |
| CORTEX_API_KEY | No | Your per-tenant Cortex API key (starts with cortex_). Required for Cortex tools in local mode. | |
| CORTEX_API_URL | No | The base URL for the Cortex API. Defaults to https://api.cortex.nexxupp.com. | |
| MCP_PUBLIC_URL | No | Public URL of the server, required in hosted mode for OAuth discovery. | |
| NEXXUPP_API_URL | No | The base URL for the Nexxupp API. Defaults to https://api.nexxupp.com. | |
| NEXXUPP_PASSWORD | No | Your Nexxupp password. Required for NWS + Calendar tools in local mode. | |
| MCP_MAX_BODY_BYTES | No | Maximum request body size in bytes. Default is 1048576. | |
| MCP_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds. Default is 60000. | |
| MCP_UPSTREAM_TIMEOUT_MS | No | Upstream timeout in milliseconds. Default is 20000. |
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 |
|---|---|
| cortex_memory_storeA | Store one user memory in Cortex. Returns the versioned brick. Scope every call to the end user's id. |
| cortex_memory_searchB | Hybrid recall over a user's Cortex memory. Returns ranked, cited bricks. |
| cortex_turnC | Stateful Cortex turn over a session. Use for multi-step flows that must stay coherent. |
| nws_searchB | Full-text search across NWS stations. Narrow with stationId when known. |
| nws_summarize_stationC | Summarize everything in an NWS station: pages, tasks, databases. |
| nws_create_taskC | Create a task in an NWS station. |
| nws_open_page_for_eventC | Open (or create) the NWS page linked to a calendar event. |
| nws_search_blocksC | Search page blocks inside NWS stations. |
| nws_read_databaseC | Read an NWS database schema plus rows, optionally through a view. |
| nws_upsert_rowsA | Create or update NWS database rows. Omit row_id to insert; set it to update. Read the database first for property ids. |
| nws_create_chartC | Create a chart block on an NWS page from a data source payload. |
| nws_apply_template_blocksC | Append template blocks to an NWS page. |
| nws_summarize_databaseC | Summarize an NWS database's contents, optionally through a view. |
| nws_station_assistB | Ask the NWS station AI to act: create/update pages, tasks, reminders, invites. Describe the goal in plain language. |
| nws_list_stationsB | List the NWS stations the user can access. |
| calendar_list_calendarsB | List the calendars the user can access. |
| calendar_list_eventsB | List events on a calendar in a time range. Optional text search. |
| calendar_create_eventC | Create an event on a calendar. |
| calendar_update_eventC | Update an event. Only set the fields to change. |
| calendar_delete_eventC | Delete an event by id. |
| calendar_ai_assistB | Ask the calendar AI in plain language: schedule, reschedule, find free time, summarize. It reads the calendar and returns executable actions. |
| billing_usageA | Check the caller's wallet before expensive runs: credit balance, tier, storage used vs quota, turns used, spend by product. Read-only; it never spends. |
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 22 tools
Most tools are distinct by prefix and purpose, but nws_station_assist and nws_create_task/calendar_ai_assist vs calendar_create_event overlap—the AI-assist tools can perform the same actions as the explicit CRUD tools, creating ambiguity about which to use for a given operation.
Names consistently follow prefix_verb_noun (nws_, cortex_, calendar_, billing_) with snake_case throughout, which is predictable and readable. Minor deviation: billing_usage lacks a verb, but overall the convention is well-maintained.
22 tools for a multi-domain server (NWS, Cortex, Calendar, billing) is slightly heavy but reasonable given it spans three distinct product areas. Nothing feels gratuitous, though the set could be trimmed by removing redundant AI-assist/CRUD overlaps.
Coverage is broad and mostly complete: NWS has create/search/summarize/read/upsert plus AI assist; Calendar has full CRUD plus list and AI assist; Cortex has store/search/turn; billing has usage. Minor gaps like calendar delete exists but no explicit NWS delete tool, and Cortex lacks a delete/forget operation.