Koskamo

Jawwws Bytes MCP MCP server

This official MCP server allows AI assistants to interact with Jawwws Bytes workspaces. It enables users to read and manage links, QR codes, activity groups, and tags through delegated OAuth authorization, supporting tools for listing, creating, updating, and archiving links and tags.

Endpoint and access

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

OAuth sign-inEndpoint checked 2026-10-05Operated by Jawwws Bytes
MCP endpoint (Streamable HTTP)
https://api.jaww.ws/mcp
Vendor documentation

What you can do with it

  • List and retrieve links and QR codes
  • Create, update, and archive links
  • Manage tags and attach them to links
  • Read activity groups and tags

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http jawwws-bytes-mcp https://api.jaww.ws/mcp

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 jawwws-bytes-mcp --url https://api.jaww.ws/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable jawwws-bytes-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "jawwws-bytes-mcp": {
      "url": "https://api.jaww.ws/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "jawwws-bytes-mcp": {
      "type": "streamableHttp",
      "url": "https://api.jaww.ws/mcp",
      "disabled": false
    }
  }
}

VS Code

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

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 jawwws-bytes-mcp https://api.jaww.ws/mcp

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": {
    "jawwws-bytes-mcp": {
      "url": "https://api.jaww.ws/mcp"
    }
  }
}

Windsurf

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

Do you run Jawwws Bytes 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