Koskamo

Knapsack MCP

The Knapsack MCP server allows agents to manage organizations, workspaces, attachments, invitations, teams, and tags. It provides tools for creating and managing design system resources, enabling agents to configure and maintain the structural components of a design system without accessing the design context itself.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Knapsack MCP logo, by KnapsackVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Knapsack
You need:OAuth sign-in or a workspace API key
MCP endpoint (Streamable HTTP)
https://knapsack.sh/mcp/manage
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to knapsack.sh ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Create and manage design system organizations
  • Set up workspaces and teams
  • Manage attachments and invitations
  • Configure tags for design resources

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: sh.knapsack/knapsack@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-02: 3 of 3 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
154 ms
95th percentile latency
154 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 154 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http knapsack-mcp https://knapsack.sh/mcp/manage

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add knapsack-mcp --url https://knapsack.sh/mcp/manage

Cursor

Merge this server into .cursor/mcp.json in your project, then enable knapsack-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "knapsack-mcp": {
      "url": "https://knapsack.sh/mcp/manage"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "knapsack-mcp": {
      "type": "streamableHttp",
      "url": "https://knapsack.sh/mcp/manage",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start knapsack-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "knapsack-mcp": {
      "type": "http",
      "url": "https://knapsack.sh/mcp/manage"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http knapsack-mcp https://knapsack.sh/mcp/manage

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "knapsack-mcp": {
      "url": "https://knapsack.sh/mcp/manage"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "knapsack-mcp": {
      "serverUrl": "https://knapsack.sh/mcp/manage"
    }
  }
}

Let your agent find its tools

Find servers like Knapsack MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 532

Do you run Knapsack MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing