Git vs Nestr MCP

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

Git logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth requiredNestr MCP logoNestr MCPCommunication · Local subprocess (stdio)Connect AI to Nestr for Holacracy, Sociocracy, and self-organizing teams.60GoodAuth: api key required

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

Which MCP server should you choose?

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

Nestr MCP logoChoose Nestr MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: NESTR_API_KEY, NESTR_OAUTH_TOKEN.
  • You want tools like nestr_list_workspaces, nestr_get_workspace, nestr_create_workspace.
Explore Nestr MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitNestr MCP logoNestr MCP
CategoryVersion ControlCommunication
Quality signal81/100 · Excellent60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredAPI key required
PricingFreeNot declared
Required env varsNone listedNESTR_API_KEYNESTR_OAUTH_TOKEN
Verified owner VerifiedCommunity listing
GitHub stars91,5506
Directory activity 53 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1669

Tools & capabilities

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

Nestr MCP tools 69

  • nestr_list_workspacesList accessible workspaces
  • nestr_get_workspaceGet workspace details
  • nestr_create_workspaceCreate a new workspace (OAuth only)
  • nestr_searchSearch for nests (tasks, projects, roles)
  • nestr_get_meGet current user identity and workspace list
  • nestr_get_nestGet details of a specific nest (supports batch fetch with comma-separated IDs; single-nest `provenance`/`rights`/`whoCan` flags available)
  • nestr_explain_nestDiagnose one nest: field/property provenance (which label/circle defines each), the caller's composed rights with a deny trace, and (with `whoCan`) who can act on it and who to contact
  • nestr_get_nest_childrenGet child nests
  • nestr_create_nestCreate a new nest
  • nestr_update_nestUpdate nest properties
  • nestr_delete_nestDelete a nest
  • nestr_reorder_nestReorder a nest relative to another
  • +57 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.

Git

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

Nestr MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-348": {
      "command": "npx",
      "args": [
        "-y",
        "@nestr/mcp"
      ],
      "env": {
        "NESTR_API_KEY": "YOUR_NESTR_API_KEY_HERE",
        "NESTR_OAUTH_TOKEN": "YOUR_NESTR_OAUTH_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Git is categorized under Version Control and uses a local stdio subprocess. Nestr MCP belongs to Communication and uses a local stdio subprocess. Pick Git for version control work and Nestr MCP for communication.

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.

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

On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 53 views, 0 installs and 91,550 GitHub stars. Nestr MCP has 60/100 (Good) with 0 views, 0 installs and 6 GitHub stars.