Skip to main content
Glama

DevPilot

DevPilot is an AI agent built on top of the Model Context Protocol (MCP). It uses an LLM to reason about a user's request, invokes the appropriate MCP tools, observes their results, and continues this reasoning loop until it can produce a final answer.


Architecture

                   User
                     │
                     ▼
          Conversation Manager
                     │
                     ▼
              Tool Registry (MCP)
                     │
        list_tools() + inputSchema
                     │
                     ▼
                 LLM (Planner)
                     │
     ┌───────────────┴────────────────┐
     │                                │
     ▼                                ▼
 Tool Call(s)                  Final Answer
     │                                │
     ▼                                ▼
  Executor                         Exit
     │
     ▼
 Tool Result(s)
     │
     ▼
Conversation Manager
     │
     └───────────────► Back to LLM

Components

Conversation Manager

Maintains the complete conversation history.

Stores:

  • User messages

  • Assistant messages

  • Tool calls

  • Tool results

This conversation is sent to the LLM on every iteration.


Related MCP server: My Coding Buddy MCP Server

Tool Registry

Discovers available MCP tools.

Provides:

  • Tool name

  • Description

  • Input schema

  • Required arguments

Example:

git_status
docker_logs
fs_read_file
docker_ps
...

LLM

The LLM acts as the planner.

It receives:

  • Conversation history

  • Available tools

  • Tool schemas

It decides whether to:

  • Call one or more tools

  • Ask for clarification

  • Return the final answer


Executor

Executes tool calls returned by the LLM.

Input:

ToolCall

Output:

ToolResult

Execution Flow

User
 │
 ▼
Conversation Manager
 │
 ▼
LLM
 │
 ├── Final Answer ─────────────► Return Response
 │
 └── Tool Call
        │
        ▼
    Executor
        │
        ▼
   Tool Result
        │
        ▼
Conversation Manager
        │
        ▼
       LLM

The cycle continues until the LLM returns a final answer.


Request Flow

User:
Why is my backend container failing?

LLM

Call docker_ps()

Executor

backend -> exited
db -> running

Conversation Updated

LLM

Call docker_logs(container="backend")

Executor

panic:
database connection refused

Conversation Updated

LLM

Final Answer

The backend container exits because it cannot connect to the database.

LLM Response Types

The LLM can return one of the following responses.

Tool Call

{
    "status": "tool_call",
    "tool_calls": [
        {
            "tool_name": "docker_logs",
            "tool_args": {
                "container": "backend"
            }
        }
    ]
}

Final Answer

{
    "status": "final_answer",
    "answer": "The backend container exits because it cannot connect to the database."
}

Clarification

{
    "status": "clarification",
    "answer": "Which repository do you want to inspect?"
}

Error

{
    "status": "error",
    "answer": "Unable to execute the requested tool."
}

Agent Loop

conversation.add_user(prompt)

tools = registry.list_tools()

while True:

    response = llm.chat(
        conversation,
        tools
    )

    if response.status == "final_answer":
        return response.answer

    if response.status == "clarification":
        return response.answer

    tool_results = executor.execute(
        response.tool_calls
    )

    conversation.add_tool_calls(
        response.tool_calls
    )

    conversation.add_tool_results(
        tool_results
    )

Design Principles

  • LLM is responsible for reasoning.

  • MCP tools are responsible for execution.

  • Executor never makes decisions.

  • Conversation history is preserved across iterations.

  • Tool execution is deterministic.

  • The agent loops until a final answer is produced.

F
license - not found
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    A comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.
    Last updated
    30
    2
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    A personal AI coding assistant that connects to various development environments and helps automate tasks, provide codebase insights, and improve coding decisions by leveraging the Model Context Protocol.
    Last updated
    10
  • A
    license
    -
    quality
    C
    maintenance
    A comprehensive Model Context Protocol toolkit that transforms AI assistants into autonomous agents capable of executing real-world tasks across filesystems, web requests, Git workflows, databases, system commands, and AI integrations.
    Last updated
    MIT

View all related MCP servers

Related MCP Connectors

  • A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

  • User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.

  • A Model Context Protocol server for Wix AI tools

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/walianitin/Dev-Mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server