Skip to main content
Glama
ludoplex

agent-services-mcp

by ludoplex

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEVPROJECT_ROOTNoProject root directory~/DevProject
AGENT_TEMPLATES_DIRNoCustom templates directoryAuto-detected

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
git_new_repoB

Create a new GitHub repository with optional backup remote. Saves ~950 tokens vs agent-generated commands.

git_import_repoB

Clone an existing GitHub repository and configure backup remote. Saves ~470 tokens.

git_new_branchB

Create a new branch and push to all configured remotes. Saves ~280 tokens.

git_archive_repoC

Archive a repository with final backup push. Saves ~375 tokens.

git_sync_backupC

Sync local repositories to their backup remotes. Saves ~280 tokens.

templates_listA

List available agent instruction templates

templates_getC

Get the content of an agent instruction template

project_structureB

Get the directory structure of a project

search_filesC

Search for files by name pattern

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: git operations cover different actions (archive, import, new branch, new repo, sync backup), project tools (structure, search) are separate, and template tools (list, get) are distinct. No overlap between tools.

Naming Consistency4/5

Most tools follow a verb_noun pattern with domain prefixes (git_, templates_), except project_structure and search_files which lack a prefix. While all use snake_case and are readable, the inconsistent prefix usage slightly reduces consistency.

Tool Count5/5

9 tools is well-scoped for a server covering git operations, project exploration, and template management. Each tool serves a clear purpose without being excessive or insufficient for the apparent domain.

Completeness3/5

The tool set covers core git workflows (create, import, branch, archive, sync) and basic project access, but lacks delete operations, file read/write, and template creation/update, leaving notable gaps for full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues