Log inSubmit server

Planhat MCP vs Git

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

Planhat MCP logoPlanhat MCPCustomer Data PlatformsConnect Planhat CRM to Claude and other MCP clients with 60 local tools across 12 resource types.33EmergingAuth: not declaredGit logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth required

Verdict: choose Planhat MCP for customer data platforms 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?

Planhat MCP logoChoose Planhat MCP when

  • You need dedicated capabilities in the Customer Data Platforms domain.
  • You have the keys it needs: PLANHAT_TOKEN.
Explore Planhat MCP

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.

SpecPlanhat MCP logoPlanhat MCPGit logoGit
CategoryCustomer Data PlatformsVersion Control
Quality signal33/100 · Emerging81/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsPLANHAT_TOKENNone listed
Verified ownerCommunity listing Verified
GitHub stars091,512
Directory activity 1 views 0 installs 0 upvotes 49 views 0 installs 0 upvotes
ToolsNot listed16
Full listingView Planhat MCP View Git

Tools & capabilities

Planhat MCP 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.

Planhat MCP

No confirmed install command for Planhat MCP 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

Planhat MCP is categorized under Customer Data Platforms and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Planhat MCP for customer data platforms 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. Planhat MCP has no confirmed install command yet — follow its own setup instructions.

Planhat MCP 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 planhat-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Planhat MCP has a quality signal of 33/100 (Emerging) with 1 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 Planhat MCP

Popular comparisons with Git