Skip to main content
Glama
PuemMTH

mcp-commands

by PuemMTH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PORTNoPort used for SSE mode.8432
DATABASE_URLNoPostgreSQL DSN for the database connection.postgresql://mcp_commands:mcp_commands@localhost:5432/mcp_commands
MCP_TRANSPORTNoTransport mode, either 'stdio' or 'sse'.stdio

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
log_command_toolA
Log one AI command usage.

Args:
    command:  The command name, e.g. '/commit', '/recap', 'deep-research'
    category: Optional group, e.g. 'git', 'research', 'oracle', 'session'
    context:  Optional free-text note about where/why it was used
get_history_toolA
Get recent command-usage history.

Args:
    limit:    Max rows to return (default 20)
    command:  Filter by command name (partial match)
    category: Filter by category (exact match)
get_stats_toolA
Get command usage statistics.

Args:
    top_n: How many top items to show per category (default 10)

Returns JSON with:
- total usage count
- top commands ranked by usage
- top categories ranked by usage
- daily counts for the last 7 days
search_commands_toolB
Search command history by keyword.

Searches across command name, category, and context fields.

Args:
    query: Search keyword
    limit: Max results (default 20)
delete_command_toolC
Delete a command-usage record by its id.

Args:
    row_id: The id field from history records

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

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct purpose with no overlap: delete_command_tool removes records, get_history_tool retrieves recent history, get_stats_tool provides aggregated statistics, log_command_tool logs new usage, and search_commands_tool searches across fields. The descriptions clearly differentiate their functions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., delete_command_tool, get_history_tool, log_command_tool). The naming is uniform throughout, using snake_case and clear action-object combinations, which aids predictability and readability.

Tool Count5/5

With 5 tools, the server is well-scoped for managing command-usage history, covering logging, retrieval, deletion, search, and statistics. Each tool earns its place without being too sparse or bloated, fitting typical MCP server ranges.

Completeness4/5

The tool set provides comprehensive coverage for the command-usage domain, including create (log), read (get_history, get_stats, search), and delete operations. A minor gap is the lack of an update tool for modifying existing records, but agents can work around this by deleting and re-logging if needed.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources