Skip to main content
Glama
Blockchainpreneur

actions-xyz-mcp

by Blockchainpreneur
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

actions-xyz-mcp

MCP server for actions.xyz — give any MCP-capable agent (Claude, Cursor, Windsurf, …) the ability to extract structured action items from meeting transcripts and notes.

Demo: a meeting transcript pasted into the actions.xyz extractor, returning structured action items

The same extraction pipeline the MCP tool calls, shown in the free web tool: paste a transcript → extract → structured action items.

It exposes one tool, extract_action_items, backed by the same extraction pipeline that powers the actions.xyz product (also available as a free web tool) — not a separate toy prompt.

What it does

extract_action_items({ transcript: string })

Sends your transcript to the public actions.xyz extraction API (POST /api/tools/extract) and returns:

  1. A human-readable summary — numbered action items with priority, assignee, and due date.

  2. Structured JSON:

{
  "actions": [
    {
      "task": "Ship the MCP server package",
      "description": "CONTEXT: ...\nSTEPS:\n1. ...",
      "assignee": "Luis",
      "assigneeType": "human",
      "priority": "high",
      "tag": "engineering",
      "dueDate": "Friday"
    }
  ],
  "participants": ["Luis", "Ana"],
  "remaining": 9
}

assigneeType is "human" or "agent", priority is "high" | "med" | "low", and remaining is your free-tier quota left today.

Related MCP server: FathomBridge

Quick start

Requires Node.js ≥ 18. No API key needed. The package is installed straight from GitHub (it is not on the npm registry yet):

npx -y github:Blockchainpreneur/actions-xyz-mcp

The server speaks MCP over stdio — it is meant to be launched by your MCP client, not run by hand.

Install in your client

Claude Code

claude mcp add actions-xyz -- npx -y github:Blockchainpreneur/actions-xyz-mcp

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "actions-xyz": {
      "command": "npx",
      "args": ["-y", "github:Blockchainpreneur/actions-xyz-mcp"]
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

{
  "mcpServers": {
    "actions-xyz": {
      "command": "npx",
      "args": ["-y", "github:Blockchainpreneur/actions-xyz-mcp"]
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "actions-xyz": {
      "command": "npx",
      "args": ["-y", "github:Blockchainpreneur/actions-xyz-mcp"]
    }
  }
}

Rate limits (free tier)

The public endpoint is free and unauthenticated, with honest limits:

Limit

Value

Extractions per day

10 per IP (resets 24 h after first use)

Max transcript size

20,000 characters per call

When you hit the daily limit the tool returns a clear error with the retry window. Need more? Sign up free at actions.xyz for 5 full meetings a month.

Error handling

The tool maps every API error to a message the calling agent can act on:

Condition

What the tool tells the agent

Empty transcript

Asks for actual transcript text (caught locally, no quota burned)

Transcript > 20k chars

Says to split into chunks (caught locally, no quota burned)

429 rate_limited

Daily limit reached + when to retry (Retry-After)

503 extraction_unavailable

Service temporarily down — retry later, input is fine

500 extraction_failed

Transient server failure — retry once

Network failure / timeout

Endpoint unreachable + how to point at another deployment

Configuration

Env var

Default

Purpose

ACTIONS_XYZ_BASE_URL

https://actionsxyz.vercel.app

Base URL of the actions.xyz deployment to call (useful for self-hosted or local instances)

Development

git clone https://github.com/Blockchainpreneur/actions-xyz-mcp
cd actions-xyz-mcp
npm install
npm run build   # tsc → dist/
npm test        # real stdio handshake + live tools/call smoke test

Built by an autonomous agent

This package was designed, built, and tested end-to-end by an autonomous coding agent as part of the actions.xyz build. Every step is on the public record: actions.xyz build log.

Links

License

MIT

Available Tools

1 tool
extract_action_itemsExtract 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
transcriptYesMeeting transcript or notes to extract action items from (max 20,000 characters).

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses free tier limitations (10 extractions/day per IP, max 20,000 characters per call) and gives a JSON output structure. This provides substantial transparency into the tool's behavior beyond the basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loading the core purpose and then providing important details in a structured manner. Every part is necessary and there is no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there are no annotations, no output schema, and only one parameter, the description covers the essential aspects: input format, output structure, and usage limits. It could mention error handling or prerequisites, but overall it is largely complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage with a brief description. The tool description adds meaningful context: the input can be a transcript or free-form notes, and it specifies the max character limit. The detailed output format explanation compensates for the lack of an output schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool extracts structured action items from meeting transcripts or free-form notes. It specifies the output format and mentions the actions.xyz extraction pipeline, distinguishing the tool's purpose effectively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for meeting transcripts or notes but does not explicitly state when to use or avoid this tool. There are no sibling tools to contrast against, so the lack of alternative guidance is not penalized heavily, but some explicit usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools.

Naming Consistency5/5

Single tool name is clear and consistent with itself.

Tool Count2/5

A single tool for a server named 'actions-xyz-mcp' seems insufficient; the scope is too narrow for typical action management workflows.

Completeness2/5

The server only provides extraction, missing other essential actions like listing, updating, or deleting action items, leaving significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Blockchainpreneur/actions-xyz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server