Dobby

io.github.gil-dobbyPublished by GitHub account gil-dobbyv1.2.0Updated Oct 27, 2026

Connect, monitor, and control AI agents — tasks, approvals, schedules, and governance.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

Dobby connects an assistant to the Dobby platform to monitor and control AI agents, including tasks, approvals, schedules and governance.

What you can do
  • Connect to the Dobby platform and work with its AI agents
  • Monitor and control running agents
  • Handle tasks and approval requests
  • Manage schedules and governance settings
  • Available as a hosted remote endpoint or a local npm package
When to use it
Useful when you already run AI agents on the Dobby platform and want an assistant to check on them, act on approvals, or adjust tasks and schedules from the same conversation.
Requirements
A Dobby account with OAuth authentication. The local npm package also needs Node.js and the environment variables DOBBY_API_KEY and DOBBY_TENANT_ID, with DOBBY_API_URL optional. Network access to the Dobby platform.
Before you install
Requires a Dobby API key, which may be a live tenant key or a gateway key, plus a tenant ID; treat both as secrets. The server can control agents and act on approvals, so changes may affect real workloads. Agent data is sent to the Dobby platform.

Installation

In SourceWeft

  1. Open Dobby in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.gil-dobby%2Fdobby/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dobby": {
      "type": "http",
      "url": "https://mcp.dobby-ai.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.