Skip to main content
Glama
m-dev-tools

m-dev-tools-mcp

Official
by m-dev-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
route_intentA

Return typed IDs matching the plain-English intent.

Example: route_intent("parse JSON in M") returns ["module:m-stdlib#STDJSON"]. Results are [primary, *see_also] from the matched task_index row.

describeA

Return a pointer-blob for a typed ID.

Supported kinds: tool: / module: / cmd: / recipe:. Does not inline payloads — returns URLs the caller should fetch next, keeping the catalog's "pointers, not facts" invariant.

verifyA

List the verification_commands declared in a repo's repo.meta.json.

Accepts either a bare repo slug (m-cli) or a typed ID (tool:m-cli). Does NOT execute the commands.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: describe returns pointers for typed IDs, route_intent maps natural language to IDs, and verify lists repo verification commands. No overlap is evident.

Naming Consistency5/5

All tool names are single imperative verbs or verb_noun pairs (route_intent). The naming pattern is consistent and predictable, with no mixed conventions.

Tool Count4/5

With only 3 tools, the set is on the lower end of the typical 3-15 range, but each tool serves a focused role within the catalog domain. Slightly thin but not insufficient.

Completeness4/5

The tools cover key query operations (describing, routing, verifying) for the catalog. Missing a tool to list all known kinds or types, but route_intent partially addresses this gap.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources