Skip to main content
Glama
jsklan

devin-api-mcp

by jsklan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to devin-api-mcp

No user-submitted related servers found.

    Related Servers

    • hermes-dsh-bridge

      Emilia-awa
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.
      357 npm
      2
      GPL 3.0

    • Grok Bot MCP Bridge

      mozzquito
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.
      MIT

    • Terminal Session Manager

      danieldoalto
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.
      15
      -

    • lunge

      thuupx
      F
      license
      Not graded
      quality
      A
      maintenance
      Agent-native API client for executing REST, GraphQL, WebSocket, SSE, and gRPC requests from MCP-capable agents, with token-efficient responses and file-based collections.
      -
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: ask_question provides AI-powered answers, read_wiki_contents retrieves full documentation, and read_wiki_structure lists available topics. There is no meaningful overlap between asking questions and reading wiki docs.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: ask_question, read_wiki_contents, read_wiki_structure. Naming is uniform and predictable.

    Tool Count5/5

    With only three tools, the server is tightly scoped to AI-powered repository Q&A and wiki access. This is well within the ideal range and each tool is essential to the core purpose.

    Completeness4/5

    The set covers the primary workflows: asking questions and reading wiki documentation. A minor gap is the lack of functionality beyond wiki content (e.g., general repository file browsing), but for the stated AI Q&A focus it is sufficient.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources