Gency MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add gency-mcp -- npx -y @gency-ai/gency-mcp

{
  "mcpServers": {
    "gency-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@gency-ai/gency-mcp"
      ]
    }
  }
}

[mcp_servers.gency-mcp]
command = "npx"
args = ["-y", "@gency-ai/gency-mcp"]

{
  "mcpServers": {
    "gency-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@gency-ai/gency-mcp"
      ]
    }
  }
}

{
  "servers": {
    "gency-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@gency-ai/gency-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GENCY_API_URL (Gency API base URL), GENCY_OAUTH_CLIENT_ID (OAuth client ID override. Defaults to the built-in official client, so most users never set this), GENCY_OAUTH_CLIENT_SECRET (OAuth client secret, only needed for confidential clients), GENCY_OAUTH_API_BASE (OAuth provider base URL. Defaults to GENCY_API_URL), GENCY_OAUTH_SCOPE (Space-separated OAuth scopes), GENCY_MCP_ALLOWED_CLIENT_IDS (serve-http only: OAuth client IDs whose tokens this server accepts (space or comma separated). Empty accepts any client), GENCY_MCP_UPLOAD_SECRET (serve-http only: HMAC key for signed upload handles. Only needed when running more than one instance, so a handle issued by one verifies on another), GENCY_MCP_OAUTH_RESOURCE (RFC 8707 resource indicator to send on authorize/token/refresh requests. Opt-in until the Gency authorization server is confirmed to accept it).