Skip to main content
Glama
ajwann

installed-api

by ajwann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to installed-api

No user-submitted related servers found.

    Related Servers

    • mcp-agent-kit

      hummbl-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables building and running zero-dependency MCP servers with automatic JSON Schema generation, exposing Python tools to Claude Desktop, Cursor, and autonomous agent fleets.
      2
      Apache 2.0

    • mcp-connect

      myat-kyaw-thu
      A
      license
      Not graded
      quality
      D
      maintenance
      A dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.
      5 npm
      6
      MIT

    • FastAPI Architect MCP

      AbdessamadTzn
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives Claude Code IDE-level intelligence for FastAPI projects — semantic code navigation, safe renaming, route inspection, dependency trees, and Pydantic model analysis. Instead of Claude reading files blindly, it calls structured tools backed by Jedi (Python language server) and Python's AST.
      19
      1
      MIT

    • mcp-cli-catalog

      abcpro1
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      5 npm
      1
      MIT

    • mcp-x

      LakshmiSravyaVedantham
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns any CLI tool or REST API into an MCP server for Claude, enabling Claude to use git, databases, or any API through natural language.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: metadata inspection (py_inspect), raw source (py_source), and version listing (py_versions) for Python; declarations (node_types) and version listing (node_versions) for Node. The py_/node_ split makes cross-language selection unambiguous, and the inspect-vs-source boundary is clear from the descriptions.

    Naming Consistency5/5

    All five tools follow a strict <lang>_<noun/verb> pattern (py_inspect, py_source, py_versions, node_types, node_versions). Prefixes group by ecosystem and suffixes consistently denote the operation, making the set highly predictable.

    Tool Count5/5

    Five tools is well-scoped for a dual-ecosystem introspection server: three for Python, two for Node, each earning its place with no redundant members. Nothing feels padded or thin for the stated purpose.

    Completeness3/5

    The Python side has both metadata inspection and source retrieval, but the Node side only offers type declarations and versions — there is no equivalent of py_source for reading installed JS implementation code. This asymmetry leaves a notable gap for agents debugging Node packages, though version and type coverage is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources