Docs / MCP

Configure gitnative for local agent workflows.

Add the gitnative MCP server, install the public skills, and commit an AGENTS.md file so development agents can retrieve workspace context without copying private project data into prompts.

Production endpoint

https://api.gitnative.dev/mcp

Setup

Connect an MCP client

Keep the key in local environment configuration and reference it from your MCP client. Do not commit the key, paste it into tickets, or store it in AGENTS.md.

  1. 1Open Settings > API / MCP Keys in the target workspace.
  2. 2Rotate or reveal your personal workspace key.
  3. 3Configure your MCP client endpoint as https://api.gitnative.dev/mcp.
  4. 4Pass the key as a bearer token in the MCP Authorization header.
  5. 5Ask the client to search workspace context and confirm results are scoped to the expected workspace.

Examples

Local configuration

MCP client JSON

{
  "mcpServers": {
    "gitnative": {
      "type": "http",
      "url": "https://api.gitnative.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${GITNATIVE_MCP_KEY}"
      }
    }
  }
}

Environment file

# .env.local
GITNATIVE_MCP_KEY=gn_mcp_your_personal_workspace_key

AGENTS.md excerpt

# AGENTS.md

Use gitnative MCP for project context before changing code:
- Search workspace decisions, tickets, incidents, and ownership context.
- Keep all MCP requests scoped to the active workspace.
- Never log or commit GITNATIVE_MCP_KEY.
- Apply the gitnative MCP skill when a task mentions tickets, delivery history, architecture decisions, or workspace knowledge.