Kwork vs MCP Abap Adt

A side-by-side look at the Kwork and MCP Abap Adt MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Kwork logoKworkDeveloper Tools · Local subprocess (stdio)Kwork freelance marketplace: browse projects, submit offers, manage orders, message clients52GoodAuth: not declaredMCP Abap Adt logoMCP Abap AdtDeveloper Tools · Local subprocess (stdio)ABAP ADT MCP server for reading SAP objects (programs, classes, tables, CDS) via ADT65GreatAuth: not declared

Verdict: choose Kwork for developer tools work as a local process; choose MCP Abap Adt for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Kwork logoChoose Kwork when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: KWORK_WRITES, KWORK_EXPECTED_USER_ID, KWORK_SITE.
  • You want tools like account_status, get_connects, discover_projects.
Explore Kwork

MCP Abap Adt logoChoose MCP Abap Adt when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SAP_URL, SAP_USERNAME, SAP_PASSWORD, SAP_CLIENT.
  • You want tools like GetProgram, GetClass, GetFunctionGroup.
Explore MCP Abap Adt

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKwork logoKworkMCP Abap Adt logoMCP Abap Adt
CategoryDeveloper ToolsDeveloper Tools
Quality signal52/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsKWORK_WRITESKWORK_EXPECTED_USER_IDKWORK_SITESAP_URLSAP_USERNAMESAP_PASSWORDSAP_CLIENT
Verified ownerCommunity listingCommunity listing
GitHub stars3200
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools416

Tools & capabilities

Kwork tools 4

  • account_statusФактический account ID, binding, готовность writes и `unresolved_write_ids
  • get_connectsАктивные и общие коннекты
  • discover_projectsfavorites`, `all` или `category_ids`, фильтры и opaque cursor
  • list_notificationsПолные группы уведомлений

MCP Abap Adt tools 16

  • GetProgramRetrieve ABAP program source code
  • GetClassRetrieve ABAP class source code
  • GetFunctionGroupRetrieve ABAP Function Group source code
  • GetFunctionRetrieve ABAP Function Module source code
  • GetStructureRetrieve ABAP Structure
  • GetTableRetrieve ABAP table structure
  • GetTableContentsRetrieve contents of an ABAP table
  • GetPackageRetrieve ABAP package details
  • GetTypeInfoRetrieve ABAP type information
  • GetIncludeRetrieve ABAP Include Source Code
  • SearchObjectSearch for ABAP objects using quick search
  • GetTransactionRetrieve ABAP transaction details
  • +4 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Kwork

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kwork": {
      "command": "uvx",
      "args": [
        "kwork-mcp@1.5.2"
      ],
      "env": {
        "KWORK_WRITES": "YOUR_KWORK_WRITES_HERE",
        "KWORK_EXPECTED_USER_ID": "YOUR_KWORK_EXPECTED_USER_ID_HERE",
        "KWORK_SITE": "YOUR_KWORK_SITE_HERE"
      }
    }
  }
}

MCP Abap Adt

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-abap-adt-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-abap-adt"
      ],
      "env": {
        "SAP_URL": "YOUR_SAP_URL_HERE",
        "SAP_USERNAME": "YOUR_SAP_USERNAME_HERE",
        "SAP_PASSWORD": "YOUR_SAP_PASSWORD_HERE",
        "SAP_CLIENT": "YOUR_SAP_CLIENT_HERE"
      }
    }
  }
}

Frequently asked questions

Kwork is categorized under Developer Tools and uses a local stdio subprocess. MCP Abap Adt belongs to Developer Tools and uses a local stdio subprocess. Pick Kwork for developer tools work and MCP Abap Adt for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Kwork has no declared pricing — check the project's own site. MCP Abap Adt has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add kwork and mcp-abap-adt-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kwork has a quality signal of 52/100 (Good) with 0 views, 0 installs and 3 GitHub stars. MCP Abap Adt has 65/100 (Great) with 2 views, 0 installs and 200 GitHub stars.