English Français العربية

Baton

Official registry Developer tools

Local MCP server for Baton: edit git-native API requests, collections, environments and scripts.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @dudko.dev/baton-mcp
Claude Code 
claude mcp add baton -- npx -y @dudko.dev/baton-mcp@0.2.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "baton": {
            "command": "npx",
            "args": [
                "-y",
                "@dudko.dev/baton-mcp@0.2.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Baton — MCP setup
  2. What you can do
  3. Install in Claude Code (plugin)
  4. Connect from other clients
  5. Safety
  6. Troubleshooting
  7. Support

Baton — MCP setup

Let your AI assistant work in a Baton workspace. Baton is a git-native API client (a Postman alternative): requests, collections and environments are plain YAML files in a repository you own. The MCP server runs locally, edits those files the same way the app does, and every change shows up in the app instantly and goes through git review like any other change.

  • Server: baton
  • Transport: stdio (local process)
  • Package: @dudko.dev/baton-mcp — Node.js 24+
  • Auth: none — it runs locally with your user's permissions; secrets never pass through it.

What you can do

By default the assistant can read and write the workspace but not send requests:

ToolWhat it does
workspace_infoOrientation: name, settings, environments, collection tree.
list_requestsRequests with method, URL and tags.
get_requestA parsed request plus its raw YAML — secrets appear as references only.
upsert_requestWrite a request as deterministic YAML.
move_requestMove or rename a request, keeping its id.
delete_requestDelete a request.
upsert_collectionCreate or update a collection or folder.
list_environmentsEnvironments, with secret names only.
upsert_environmentWrite an environment (secret names only).
get_script / upsert_scriptRead and write pre-request and test scripts.
run_request / run_collectionExecute a request or a collection — only with --allow-run.

Install in Claude Code (plugin)

/plugin marketplace add dudko-dev/baton-mcp-setup
/plugin install baton@baton
/reload-plugins

The plugin starts the server in the current project directory, so open Claude Code in (or under) your Baton workspace. To point it elsewhere, or to let the assistant execute requests, add the server by hand instead (below) with --workspace <dir> and/or --allow-run.

Prefer not to use the marketplace? Add the server directly:

claude mcp add baton -- npx -y @dudko.dev/baton-mcp --workspace /path/to/workspace

Connect from other clients

Claude Desktop

claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "baton": {
      "command": "npx",
      "args": [
        "-y",
        "@dudko.dev/baton-mcp"
      ]
    }
  }
}
Cursor

~/.cursor/mcp.json or .cursor/mcp.json:

{
  "mcpServers": {
    "baton": {
      "command": "npx",
      "args": [
        "-y",
        "@dudko.dev/baton-mcp"
      ]
    }
  }
}
VS Code (GitHub Copilot / MCP) and other clients
{
  "servers": {
    "baton": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dudko.dev/baton-mcp"
      ]
    }
  }
}

Safety

  • Running requests is off by default. Add --allow-run to the args only when you want the assistant to fire requests — editing files should never silently send traffic.
  • Secrets stay out of the workspace. The server reads and writes secret names and {{secret:name}} references only; a plaintext value where a reference belongs is refused.
  • The server never touches git. Commits stay yours.
FlagMeaning
--workspace <dir>Workspace folder (default: current directory).
--allow-runLet the agent execute requests. Off by default.

Troubleshooting

  • "not a Baton workspace" / the client says "Connection closed" — the server exits at start when the folder has no baton.yaml. Open Claude Code in your workspace, or add the server by hand with --workspace /path/to/workspace.
  • run_request refuses — add --allow-run.
  • npm warn EBADENGINE … required: { node: '>=24' }, then nothing — the server needs Node.js 24+; node --version in the shell your client starts.

Support

Frequently asked questions

What is Baton?

Local MCP server for Baton: edit git-native API requests, collections, environments and scripts.

How do I install Baton?

It runs on your machine. In Claude Code: claude mcp add baton -- npx -y @dudko.dev/baton-mcp@0.2.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Baton need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Baton open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Baton?

It is published by dudko-dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.