English Français العربية

Jwt

Registre officiel Autres

JWT decoder MCP.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http jwt 'https://gateway.pipeworx.io/jwt/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jwt": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/jwt/mcp"
        }
    }
}
NPM package @pipeworx/mcp-jwt
Claude Code 
claude mcp add jwt -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-jwt@0.2.1
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jwt": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-jwt@0.2.1"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

Variables d'environnement

  • PIPEWORX_API_KEY secret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. mcp-jwt
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-jwt

JWT decoder MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

ToolDescription
decode_jwtDecode a JSON Web Token (keyless, offline): returns the header and payload JSON plus a summary of the standard claims (iss, sub, aud, exp/iat/nbf as ISO dates, and whether it is expired). NOTE: this decodes but does NOT verify the signature — a decoded token is not a verified/trusted token.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "jwt": {
      "url": "https://gateway.pipeworx.io/jwt/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/jwt/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/decode_jwt \
  -H 'Content-Type: application/json' \
  -d '{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/decode_jwt. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-jwt

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Jwt data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Questions fréquentes

Qu'est-ce que Jwt ?

JWT decoder MCP.

Comment installer Jwt ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http jwt 'https://gateway.pipeworx.io/jwt/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Jwt ?

Oui. Il attend PIPEWORX_API_KEY, à renseigner dans sa configuration.

Jwt est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Jwt ?

Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.