Lightweight MCP server to give you access to the Stakpak API.
Lightweight MCP server to give you access to the Stakpak API. Exposed over MCP by the stakpak mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Before using the MCP server, you'll need to obtain a Stakpak API key. You can get your API key by:
Everything the assistant can do here goes through one of these:
Cursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serverGeneration — The Generation tool exposed by this serverDevelopment — The Development tool exposed by this server@stakpak/mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: STAKPAK_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stakpak's toolset — Cursor, Windsurf, Generation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by stakpak; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| Generation | The Generation tool exposed by this server. |
| Development | The Development tool exposed by this server. |
{
"mcpServers": {
"stakpak": {
"command": "npx",
"args": ["@stakpak/mcp@latest", "--output=resource"],
"env": {
"STAKPAK_API_KEY": "<your-stakpak-api-key>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| STAKPAK_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.