qorami-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QORAMI_API_KEY | Yes | Your Qorami API key, obtainable from the dashboard at https://qorami.fr/dashboard/ |
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 |
|---|---|
| verify_emailA | Before sending ANY email, call this to get permission from Qorami. Returns a decision the agent MUST obey: send (allowed), request_human_confirmation (a human must approve first — then poll check_action_status), or do_not_send (blocked). When not allowed, "suggestions" says what to fix. |
| check_action_statusA | After request_human_confirmation, poll this with the actionId until nextAction.type becomes "send" (approved) or "do_not_send" (blocked). |
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 2 tools
The two tools have clearly distinct purposes: verify_email handles the initial permission check, and check_action_status polls the result of a human confirmation request. There is no overlap.
Both tool names follow the verb_noun pattern (verify_email, check_action_status) and use snake_case consistently.
With only 2 tools, the set is on the thin side for a standalone MCP server, but it covers the core email verification workflow without unnecessary additions.
The tools cover the entire permission lifecycle: initial decision via verify_email and subsequent polling for human confirmation via check_action_status. No obvious gaps for the intended domain.