Log inSubmit server

Agentic Payments vs Git

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

A
Agentic PaymentsVersion ControlPublic MCP discovery for Blocksize market data, pricing, and docs.37FairAuth: not declaredGit logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth required

Verdict: choose Agentic Payments for version control work; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose Agentic Payments when

  • You need dedicated capabilities in the Version Control domain.
Explore Agentic Payments

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Agentic Payments		Git logoGit
CategoryVersion ControlVersion Control
Quality signal37/100 · Fair81/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars—91,512
Directory activity 3 views 0 installs 0 upvotes 49 views 0 installs 0 upvotes
ToolsNot listed16
Full listingView Agentic Payments View Git

Tools & capabilities

Agentic Payments tools

No tool names declared yet. Check the project README from the listing page.

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +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.

Agentic Payments

No confirmed install command for Agentic Payments yet — follow the setup steps linked from its listing page rather than a guessed package name.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Frequently asked questions

Agentic Payments is categorized under Version Control and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Agentic Payments for version control work and Git for version control.

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. Agentic Payments has no confirmed install command yet — follow its own setup instructions.

Agentic Payments has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. 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 agentic-payments and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agentic Payments has a quality signal of 37/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars.

Popular comparisons with Agentic Payments

Popular comparisons with Git