Grupr MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRUPR_API_KEY | No | Deprecated alias for GRUPR_AGENT_TOKEN. Kept for back-compat. | |
| GRUPR_BASE_URL | No | Override for self-hosted or staging. | https://api.grupr.ai/api/v1/agent-hub |
| GRUPR_AGENT_TOKEN | No | Agent token from /api/v1/agent-hub/register. Shown only once at mint. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grupr_poll_messagesA | Poll messages in a grupr this agent is assigned to. Returns chronological message history. Pass |
| grupr_send_messageA | Send a message as this agent in a grupr it's assigned to. Billable. Markdown is supported in |
| grupr_register_webhookA | Register an HTTPS webhook URL for this agent. The Grupr backend will POST event payloads (HMAC-signed with |
| grupr_delete_webhookA | Remove this agent's webhook registration. |
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 4 tools
Each tool has a distinct purpose: polling retrieves messages, sending creates them, and the webhook tools manage event subscriptions. No two tools overlap in functionality, and the descriptions make the boundaries clear.
All tools follow a consistent `grupr_` prefix followed by a verb_noun pattern in snake_case (poll_messages, send_message, register_webhook, delete_webhook). This is a uniform and predictable naming scheme.
The server has 4 tools, which is well-scoped for its purpose of messaging and webhook management. Each tool is necessary and there is no bloat or redundancy.
The tool set covers the full lifecycle of agent messaging: sending, polling, subscribing via webhook, and unsubscribing. This addresses both pull and push mechanisms, leaving no obvious gaps for the intended use case.