Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Josh-E-S/pexip-mgmt-mcp --skill pexip-mjxgit clone --depth 1 https://github.com/Josh-E-S/pexip-mgmt-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-mjx)<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-mjx"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-mjx/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-mjx"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-mjx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00187 | $0.01745 |
| Opus 5 | $0.00093 | $0.00873 |
| Sonnet 5 | $0.00037 | $0.00349 |
| Haiku 4.5 | $0.00019 | $0.00175 |
Grade A, and why
pexip-mjx scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pexip MJX — One-Touch Join for room systems
MJX (Microsoft Join eXchange) is Pexip's room-system integration. It connects to your calendar system (Exchange Online / on-prem, or Google Workspace), reads the upcoming meetings on each room mailbox, detects video-meeting URLs/aliases inside the invite body (Pexip, Teams, Zoom, Webex, Google Meet), and pushes a normalized "Join" button to the in-room codec's UI so users tap one button instead of typing a long URI.
Three Pexip resources govern it:
mjx_endpoint— a room video system (Cisco CE, Poly OBTP, Logitech Tap, etc.) Pexip pushes the Join button tomjx_integration— the calendar source (Exchange / Google) Pexip reads frommjx_meeting_processing_rule— regex/transform rules that detect each meeting platform in the invite body and produce the dial string
The pexip-mgmt-mcp server exposes 4 dedicated MJX status tools — get_mjx_endpoint_status, list_mjx_endpoint_status, get_mjx_meeting_status, list_mjx_meeting_status (in src/pexip_mcp/tools/status.py). The MJX configuration resources (mjx_endpoint, mjx_integration, mjx_meeting_processing_rule, …) are managed through the generic *_resource CRUD tools (create_resource, get_resource, update_resource, delete_resource, list_resources).
When to use
- "Set up One-Touch Join for our conference rooms"
- "Why isn't the Join button showing up on the Webex panels?"
- "Add a rule to detect Zoom meetings in the calendar invite"
- "Migrate room systems from vendor's OTJ to Pexip MJX"
- Adding
mjx_*resource tools to the MCP server
When NOT to use
- Client-side / WebRTC join flows → out of scope for this server-side package
- VMR creation / management →
pexip-operations/vmr-administration.md - General gateway dial-plan rules (for non-room calls) →
pexip-operations/dial-plan.md
Architecture in one diagram
Exchange/O365/Google Workspace
│ calendar read
▼
┌─────────────────────────┐
│ mjx_integration │
│ (calendar source) │
└────────────┬────────────┘
│
detect meeting │ apply rules
▼
┌─────────────────────────┐
│ mjx_meeting_processing │
│ _rule (regex/transform) │
└────────────┬────────────┘
│ produces join URI
▼
┌─────────────────────────┐
│ mjx_endpoint │
│ (Cisco / Poly / …) │
│ gets "Join" button │
└─────────────────────────┘
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 115 lines · 187 tokens per session scan A 404addbc3264
pexip-mjx is a skill published in the GitHub repository Josh-E-S/pexip-mgmt-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 187 tokens to every session and 1,745 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ruview-cli-api
Use the RuView wifi-densepose CLI binary (incl. MAT scan/status/zones/survivors/alerts/export subcommands), the REST API (wifi-densepose-api, Axum), and the browser/WASM build (wifi-densepose-wasm, wifi-densepose-wasm-edge). Use when integrating RuView into another program, scripting it from the shell, exposing it…
amazon-alexa
Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home).
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
jetson-customize-pcie
Per-controller PCIe enable / disable / lanes / link-speed for a Jetson Thor or Orin custom carrier via ODMDATA + kernel-DT overlay. Do NOT use for UPHY lane allocation or endpoint-mode bring-up.
deepep-to-cam-converter
A code migration skill for replacing DeepEP communication operations with CAM operations when moving mixture-of-experts code from CUDA/NCCL to Ascend NPUs.
telnyx-iot-curl
Manage IoT SIM cards, eSIMs, data plans, and wireless connectivity. Use when building IoT/M2M solutions. This skill provides REST API (curl) examples.