Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to portkey-admin-mcp

Related Servers

  • litellm-mcp

    nikitatsym
    A
    license
    A
    quality
    A
    maintenance
    MCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.
    6
    MIT

  • @jurislm/langfuse-mcp

    jurislm
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for Langfuse providing 50 tools for prompt management, observability, instance/organization management, and metrics tracking via natural language.
    19 npm
    MIT

  • litellm-mcp

    weeebdev
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
    11 npm
    MIT

  • litellm-admin-mcp

    junwayne66
    F
    license
    Not graded
    quality
    D
    maintenance
    Exposes LiteLLM Proxy admin APIs as MCP tools for managing internal users, virtual keys, and spend logs via streamable-http, enabling agents to administer LiteLLM without custom HTTP glue.
    1
    -

  • agentforge

    doggychip
    F
    license
    A
    quality
    F
    maintenance
    MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
    5
    3
    -
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.9/5.0

Scored across 178 tools

Disambiguation4/5

Most tools follow a clear resource+action pattern, and descriptions explicitly cross-reference related tools, so typical CRUD operations are easy to distinguish. However, the sheer number of analytics tools (cost/token/latency/error/cache/user/feedback) and the MCP integration/server/capability families create some boundary ambiguity that could lead to misselection.

Naming Consistency4/5

The overwhelming majority use consistent verb_noun (get_, list_, create_, update_, delete_) with resource nouns, and longer names like update_input_guardrail_workspace_exclusions are still readable. Occasional action verbs (publish, promote, migrate, rotate, test) and a few oddities like get_analytics_group_users vs get_users_analytics break perfect uniformity but don't undermine predictability.

Tool Count1/5

178 tools is far beyond typical MCP server scope and creates a massive surface area for an agent to navigate. Even with coherent organization, the count alone is an extreme mismatch for an admin toolset and will degrade selection performance.

Completeness4/5

The surface covers essentially the full lifecycle for users, workspaces, keys, configs, prompts, integrations, guardrails, limits, MCP servers, and logs, with list/get/create/update/delete plus specialized operations. Minor gaps like no dedicated get_feedback or delete_log_export are workarounds, so the domain is thoroughly covered.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources