Skip to main content
Glama
Extiri

codemenu-mcp

by Extiri

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEMENU_API_KEYNoYour CodeMenu API key (optional if not set in CodeMenu settings)
CODEMENU_API_URLNoThe base URL for the CodeMenu API (default: http://127.0.0.1:1300/v1)http://127.0.0.1:1300/v1

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_snippetsA

List code snippets from CodeMenu without full code content (to reduce token usage). Returns id, title, description, language, abbreviation, tags, and group info.

get_snippetA

Get full details of a specific snippet by ID, including the complete code content

list_tagsB

List all tags available in CodeMenu

list_groupsB

List all groups available in CodeMenu

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a unique resource or action: get_snippet retrieves full content by ID, list_snippets returns metadata only, list_tags enumerates tags, and list_groups enumerates groups. There is no overlap in purpose, so an agent can easily select the right tool.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern with clear prefixes: get_ for single-item retrieval and list_ for collection enumeration. The naming is predictable and uniform across the set.

Tool Count4/5

Four tools is a compact set that covers reading and browsing snippets, tags, and groups. It is slightly under-scoped for a snippet manager because it omits search/filter or mutation tools, but each existing tool earns its place.

Completeness3/5

The read surface is partially complete: list_snippets and get_snippet cover snippet retrieval, and list_tags/list_groups expose metadata. However, there is no create, update, or delete for snippets, and no way to search or filter snippets by tag or group, which are notable gaps for a snippet management domain.

Maintenance

ActivityInactive
ResponsivenessNo issues