Skip to main content
Glama

asker-mcp

Your AI agent turns your definitions into a bank of questions with Asker. A definitions file drafted from your notes and checked, questions generated in GIFT or Moodle XML, and reviewed with you before they reach Moodle.

Node.js 20+ MCP server Status: in development License: MIT

asker-mcp is an MCP server for Asker, which generates many questions (true/false, multiple choice, short answer, matching, ordering) from a file of definitions: a concept's names, its definition and its tables. An AI agent drafts that file from your notes in Asker's language, checks it, runs Asker on it, and goes through the questions with you so the bad ones are left out before the moodle-teacher extension imports the rest into your question bank. The questions come from your own definitions, the same every time. It's in development and not on npm yet.

✨ Why asker-mcp

  • 📝 Your definitions, your questions. Every question traces back to a definition you wrote or approved.

  • ✅ Checked first. An input with a mistake is reported with its line, and nothing is generated.

  • 🔎 Reviewed with you. The questions by concept and type, and a copy without the ones you leave out.

  • 🎓 Ready for Moodle. GIFT or Moodle XML, for moodle-teacher's question import.

  • 🔁 Reusable. Your input files stay yours, to generate again next year.

Related MCP server: Moodle Study MCP

🧰 What's inside (planned)

Area

For example

📝 Inputs

asker_input_reference, check_input

❓ Questions

generate_questions, read_questions, exclude_questions

🔌 For agents

The asker extension in agent-extensions, with its skills and capabilities

🛠️ Developing

The plan is in .minispec/features/asker-tools.md and the main decision in ADR-005; CLAUDE.md lists every command. npm run build, npm test and npm run check before every commit. Releases are published to npm by the owner.

Made with 💖 by Falken's Lab Team

Available Tools

1 tool
server_infoServer infoA
Read-only

Show this server's name, version and data folder, and, for a server that needs programs installed apart, whether they're there. Contains no secrets.

Inputs: no named parameters. Returns: name, node, dataDir, version, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only a single tool, so there is no possibility of confusing it with another action or resource. Its purpose (reporting server metadata) is unambiguous.

    Naming Consistency4/5

    Only one name exists, so no inconsistency is possible, but 'server_info' is a noun-style identifier rather than a verb_noun pattern, making it hard to call fully predictable.

    Tool Count2/5

    A one-tool surface is extremely thin and essentially trivial; an agent gains almost no capability from this server beyond introspection. This is the 'too few (1)' end of the scale.

    Completeness4/5

    Given the narrowly stated purpose of reporting server name, version, data folder, and program-installation status, the single tool bundles all of that information. Minor gap: no separate check for individual dependencies or health beyond what one aggregate call returns.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers