diff --git a/content/docs/cli/skills/index.mdx b/content/docs/cli/skills/index.mdx index ac1457a..a7bd058 100644 --- a/content/docs/cli/skills/index.mdx +++ b/content/docs/cli/skills/index.mdx @@ -38,14 +38,20 @@ The canonical skill files live in the docs repo at `skills//SKILL.md` and ## Install +The skill files are hosted in [`webrenew/mogplex-docs`](https://github.com/webrenew/mogplex-docs) under `skills/`. Fetch them first, then copy into your agent host. + ### Claude Code ```bash +# Fetch just the skills/ tree (no full clone needed) +npx -y degit webrenew/mogplex-docs/skills mogplex-skills +cd mogplex-skills + # Global -mkdir -p ~/.claude/skills && cp -R skills/* ~/.claude/skills/ +mkdir -p ~/.claude/skills && cp -R . ~/.claude/skills/ -# Or per-project -mkdir -p .claude/skills && cp -R skills/* .claude/skills/ +# Or per-project (run from your project root, not the downloaded skills dir) +mkdir -p .claude/skills && cp -R /path/to/mogplex-skills/* .claude/skills/ ``` ### Claude Agent SDK diff --git a/content/docs/extend/index.mdx b/content/docs/extend/index.mdx index 7f9def8..7ea32c0 100644 --- a/content/docs/extend/index.mdx +++ b/content/docs/extend/index.mdx @@ -8,16 +8,16 @@ Mogplex is usable from two surfaces that ship today: the [web app](/web) and the The core question is: your teammate is in Claude Code, Cursor, or a custom Claude Agent SDK app, and wants to use their Mogplex skills, memories, or agents from there — without pasting tokens into a JSON config. What should they do? - + ## Which path is right today @@ -38,6 +38,6 @@ Skills are the recommended path until the MCP server is generally available. The ## Design principles this section follows -- **No pasted tokens.** Whether the user picks Skills or MCP, the auth flow owns the credential — either `mogplex login` writing to the OS keyring (Skills path) or OAuth 2.1 + PKCE against the browser session (MCP path). +- **No pasted tokens.** Whether the user picks Skills or MCP, the auth flow owns the credential — either `mogplex login` writing to `~/.mogplex/auth.json` (Skills path) or OAuth 2.1 + PKCE against the browser session (MCP path). In both cases the external agent never sees raw auth material. - **One source of truth per capability.** Tools, agents, skills, and memories are implemented once in the Mogplex runtime and exposed through whichever surface the host supports. Both paths call the same underlying services. - **Auth preflight is mandatory.** Both paths require a working credential before any action runs. Skills enforce it with a `command -v mogplex` + `mogplex login status` gate; MCP enforces it at the Streamable HTTP bearer-token middleware. diff --git a/content/docs/extend/mcp-server.mdx b/content/docs/extend/mcp-server.mdx index 3f7edc2..0630ab8 100644 --- a/content/docs/extend/mcp-server.mdx +++ b/content/docs/extend/mcp-server.mdx @@ -9,7 +9,11 @@ The Mogplex MCP server is in **preview design state** — not generally availabl ## What it is -A remote Model Context Protocol server running at `https://mogplex.com/mcp`. Any MCP-aware agent host (Claude Code, Cursor, Claude Desktop, opencode, custom Agent SDK apps) can connect and call Mogplex tools, agents, skills, and memories as MCP primitives — without the user pasting a token into a JSON config. +A remote Model Context Protocol server hosted by Mogplex. Any MCP-aware agent host (Claude Code, Cursor, Claude Desktop, opencode, custom Agent SDK apps) will be able to connect and call Mogplex tools, agents, skills, and memories as MCP primitives — without the user pasting a token into a JSON config. + + +The final endpoint path is not yet committed. Examples on this page use `https://mogplex.com/mcp` as a **placeholder**; the shipping URL (exact host, version prefix) will be announced in release notes and this page will be updated then. Do not wire the placeholder URL into production clients. + ## What it replaces @@ -50,17 +54,17 @@ Mogplex skills are additionally exposed as MCP **prompts**, since a skill defini ## Install (once available) -Remote Streamable HTTP — no shim, no token pasting, the host drives OAuth: +Remote Streamable HTTP — no shim, no token pasting, the host drives OAuth. The shape of the commands below is accurate; the URL is a placeholder that will be finalized when the server ships: ```bash -# Claude Code -claude mcp add --transport http mogplex https://mogplex.com/mcp +# Claude Code — replace with the final endpoint from release notes +claude mcp add --transport http mogplex # Cursor -# Settings → MCP → Add server → URL: https://mogplex.com/mcp +# Settings → MCP → Add server → URL: ``` -For hosts that don't yet speak remote MCP with OAuth, a stdio shim `npx -y @mogplex/mcp` will ship alongside. The shim runs the OAuth flow once, caches the token in the OS keyring, and proxies stdio ↔ HTTP. +For hosts that don't yet speak remote MCP with OAuth, a stdio shim `npx -y @mogplex/mcp` will ship alongside. The shim runs the OAuth flow once, stores the token in `~/.mogplex/auth.json` (same file the CLI uses), and proxies stdio ↔ HTTP. ## How it relates to Connections (inbound MCP) diff --git a/content/docs/extend/skills.mdx b/content/docs/extend/skills.mdx index b081754..48bd135 100644 --- a/content/docs/extend/skills.mdx +++ b/content/docs/extend/skills.mdx @@ -22,7 +22,7 @@ Together they cover the same capability surface the [MCP server](/extend/mcp-ser ## Why this is the right path today -- **No pasted tokens.** The `mogplex login` browser flow owns the credential and writes it to the OS keyring. The external agent never sees raw auth material. +- **No pasted tokens.** The `mogplex login` browser flow owns the credential and writes it to `~/.mogplex/auth.json` — see the [Authentication guide](/cli/guides/authentication) for precedence rules and file contents. The external agent never sees raw auth material. - **Works in every skill-aware host.** The skill format is portable: Claude Code, Claude Agent SDK, and any host that reads `SKILL.md`-style files. Cursor project rules work too by copying the skill body. - **Thin wrapper.** Skills do not duplicate Mogplex logic — they are instructions for how to call the existing CLI, which calls the existing Mogplex runtime. - **No infra dependency.** Ships the moment the CLI is on the user's `PATH`. Nothing to deploy, no tokens to provision. @@ -33,7 +33,7 @@ Together they cover the same capability surface the [MCP server](/extend/mcp-ser | --- | --- | --- | | Status | **Available** | Preview design; not live | | Protocol | Skill file + shell | MCP Streamable HTTP | -| Auth | `mogplex login` → OS keyring | OAuth 2.1 + PKCE (DCR) | +| Auth | `mogplex login` → `~/.mogplex/auth.json` | OAuth 2.1 + PKCE (DCR) | | Token pasted in config? | No | No | | Execution path | External agent shells out to `mogplex exec` | External agent calls MCP tool | | Streaming progress | `--jsonl` | MCP `notifications/progress` | @@ -44,8 +44,22 @@ When the MCP server ships, both paths will stay supported. Skills will continue ## Install +First fetch the skill files from [`webrenew/mogplex-docs`](https://github.com/webrenew/mogplex-docs). Either clone the repo or download the `skills/` tree directly: + +```bash +# Option A — clone and cd +git clone https://github.com/webrenew/mogplex-docs.git +cd mogplex-docs + +# Option B — sparse download of just the skills/ tree +npx -y degit webrenew/mogplex-docs/skills mogplex-skills +cd mogplex-skills && cd .. # or rename the dir as you like +``` + +Then copy the `skills/` contents into your agent host: + ```bash -# Global (Claude Code) +# Global (Claude Code) — run from the directory containing `skills/` mkdir -p ~/.claude/skills && cp -R skills/* ~/.claude/skills/ # Or per-project