Hosting

local

Transport

Not documented

Endpoint

Local process; no hosted endpoint documented

Authentication

Requires a Stakpak API key (STAKPAK_API_KEY), created after signing in to a Stakpak account. Store it in the client's local environment configuration; do not put it in a shared project file.

Requirements

• Stakpak account and API key
• Node.js/npm and an MCP-capable client; repository documents npx package setup

Setup steps

1. Sign in at https://stakpak.dev/ and create an API key from the profile's API keys section.
2. Add the local package to the MCP client. The official Claude Desktop example uses command npx, args ["@stakpak/mcp@latest", "--output=resource"], and env STAKPAK_API_KEY=<YOUR_API_KEY>.
3. Use the client's secure local environment/secret configuration for the key, then restart or reload the MCP client.
4. Verify with a harmless request to generate or explain a small infrastructure configuration; review generated code before applying it.

Standalone @stakpak/mcp README documents one tool, generate_infrastructure_code. Separate stakpak/agent CLI MCP supports local, remote and combined tool modes with a different, evolving tool surface; do not conflate them. Upstream package README contains an unexplained Vercel API phrase, so this record remains flagged for source clarification.

• generate_infrastructure_code

  Generate infrastructure code for a project. Stakpak documentation says the integration supports Terraform, Kubernetes, GitHub Actions, and Dockerfile configurations.

  01

• The README contains an apparent stale copy/paste inconsistency: its Tools section says ?Vercel API,? while repository title, package description, and Stakpak docs say this connects to the Stakpak API.
• The published npm package version shown by UNPKG is 0.0.4 and was last released about a year before retrieval; current maintenance/release status is uncertain.
• The tool roster in README contains one named tool; do not infer that its other broad capability descriptions are separate MCP tools.
• No runtime connection test performed.

• Repository README tool section says ?Vercel API?; official Stakpak docs and repository purpose say the MCP connects to Stakpak API. No Vercel API tool behavior is asserted.

• publisher repository

  Official Stakpak organization repo identifies a local MCP server connecting to Stakpak API, provides Claude Desktop/Cursor/Windsurf setup examples and lists generate_infrastructure_code; README has an inconsistent Vercel API phrase in its tool section.

• publisher documentation

  Stakpak docs identify the MCP server as connecting to Stakpak API and describe editing/generating Terraform, Kubernetes, GitHub Actions, and Dockerfile code; API key required.

• publisher documentation

  Official key-management guide says sign in at stakpak.dev, open profile, then API keys to create a key.

• package registry

  Package registry mirror lists @stakpak/mcp version 0.0.4 as the latest version and says it was released last year at retrieval; treat recency as a maintenance concern, not proof of abandonment.

• official cli repository

  Current Stakpak agent repository documents separate local/remote/combined MCP modes, local file/command tools and remote API-key-backed tools; this is a separate implementation from the standalone package record.

Documentation checked 2026-10-28. Connection has not been runtime tested.