actions-xyz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACTIONS_XYZ_BASE_URL | No | Base URL of the actions.xyz deployment to call (useful for self-hosted or local instances) | https://actionsxyz.vercel.app |
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 |
|---|---|
| extract_action_itemsA | Extract structured action items from a meeting transcript or free-form notes using the actions.xyz extraction pipeline. Returns a human-readable summary plus JSON: { actions: [{ task, description, assignee, assigneeType: "human"|"agent", priority: "high"|"med"|"low", tag, dueDate? }], participants: string[], remaining }. Free tier: 10 extractions/day per IP, max 20,000 characters per call. |
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
Only one tool exists, so there is no possibility of confusion with other tools.
Single tool name is clear and consistent with itself.
A single tool for a server named 'actions-xyz-mcp' seems insufficient; the scope is too narrow for typical action management workflows.
The server only provides extraction, missing other essential actions like listing, updating, or deleting action items, leaving significant gaps.