docs: add Extend section for outbound integrations (MCP + Skills)#25
docs: add Extend section for outbound integrations (MCP + Skills)#25charlesrhoward merged 1 commit intomainfrom
Conversation
New top-level Extend section covering how external agents reach Mogplex capabilities: - extend/index.mdx — hub with a Skills-vs-MCP decision table - extend/mcp-server.mdx — preview-state page for the Mogplex MCP server (Streamable HTTP, OAuth 2.1 + PKCE, DCR); documents planned endpoints, scopes, and tool surface so integrators can plan against it - extend/skills.mdx — explains Skills as today's substitute and links to the canonical files under /cli/skills Also wires the section into the top-level nav (docs/meta.json, get-started card) and adds a Callout in web/settings Connections clarifying that page is about inbound MCP, with a pointer to Extend for outbound.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![mogplex[bot]](https://avatars.githubusercontent.com/in/3107927?s=60&v=4){kind=small}
There was a problem hiding this comment.
Mogplex PR Review
Status: Attention needed
This is a well-structured documentation PR that adds a clear, coherent Extend section. The content is accurate, consistently framed, and the cross-links are all correctly wired. There are no security, correctness, or architecture issues. I'm flagging a small set of content-accuracy and maintainability concerns worth addressing before merge.
5 findings were added inline.
|
|
||
| # Or per-project | ||
| mkdir -p .claude/skills && cp -R skills/* .claude/skills/ | ||
| ``` |
There was a problem hiding this comment.
Warning: Install snippet references a skills/ source directory that may not exist or may mislead readers
The install block in extend/skills.mdx (and the identical block in cli/skills/index.mdx) tells users to run:
cp -R skills/* ~/.claude/skills/This assumes a skills/ directory exists at the root of whatever context the user is working in — which is true if they've cloned mogplex-docs, but completely wrong if they encounter this snippet from the rendered docs page while working in their own project. There's no instruction to first clone the repo or npx-fetch the skills. A reader who blindly pastes this will get a shell error with no clear recovery path.
Suggestion: Add a short prerequisite step above the snippet (e.g., "First, clone the mogplex-docs repo or download the skills archive:") or change the snippet to use a direct download/npx invocation so it works standalone. The canonical cli/skills/index.mdx already shows the right context for Agent SDK; the Claude Code block deserves the same treatment.
|
|
||
| ## What it replaces | ||
|
|
||
| The substitute available today is the **Skills** approach (see [Skills](/extend/skills)). Skills teach an external agent to drive Mogplex through the `mogplex` CLI. The MCP server path replaces that shim with a direct protocol-native integration once the host supports remote MCP with OAuth. |
There was a problem hiding this comment.
Warning: MCP server endpoint URL is a real, potentially premature public commitment
The page hard-codes https://mogplex.com/mcp as the planned endpoint URL in both prose and the install code snippet:
claude mcp add --transport http mogplex https://mogplex.com/mcpIf the final URL differs (e.g., api.mogplex.com/mcp, or versioned as /mcp/v1), this page will ship incorrect instructions and readers who try the URL early (the Callout says "not generally available" but curious readers will absolutely try it) may get confusing 404s or unexpected responses.
Suggestion: Either (a) use a clearly-placeholder URL like https://mogplex.com/mcp with an inline note that the exact path is subject to change, or (b) omit the install snippet entirely until the server ships and direct readers to release notes. The prose description of the auth model and tool surface is valuable without the code block; the code block is the part that becomes a liability if the URL changes.
| - [Skills](/extend/skills) — today's substitute | ||
| - [CLI Skills reference](/cli/skills) — canonical skill files | ||
| - [Settings → Connections](/web/settings) — inbound MCP (Mogplex as consumer) | ||
| - [MCP specification](https://modelcontextprotocol.io/specification) |
There was a problem hiding this comment.
Warning: Missing terminal period breaks last sentence of mcp-server.mdx prose
The final sentence of the "How it relates to Connections" section ends without a period:
…and Mogplex can turn around and call a Notion MCP connection from within the same logical tool call
This is a minor copy issue, but it's at the very end of the file and will be visible to readers. Add the missing period.
| "title": "Mogplex Docs", | ||
| "root": true, | ||
| "pages": ["index", "cli", "web"] | ||
| "pages": ["index", "cli", "web", "extend"] |
There was a problem hiding this comment.
Suggestion: content/docs/meta.json places extend after web — verify sidebar order matches UX intent
The updated meta.json is ["index", "cli", "web", "extend"]. The PR description says Extend should appear "between Web App and page end", which this satisfies. However the get-started cards in index.mdx now show MCP server card before Skills card:
<Card title="MCP server (preview)" … />
<Card title="Skills (available today)" … />Since Skills is the recommended path today and MCP is explicitly preview-only, putting it second in the hub card list may cause users to skip the preferred path. Consider swapping the card order so Skills appears first, consistent with the recommendation text that immediately follows the cards.
|
|
||
| | If the user's agent host… | Use | | ||
| | --- | --- | | ||
| | Is skill-aware (Claude Code, Agent SDK, Cursor project rules) | [Skills](/extend/skills) | |
There was a problem hiding this comment.
Suggestion: Exec-mode guide link in extend/index.mdx decision table may be a dead link
The decision table row for CI/shell users links to /cli/guides/exec-mode. This path is not among the changed files and was not verified in this PR. If that page does not yet exist in the docs, the link will 404. Confirm the target exists or stub it before merging, since pnpm build generating 168 pages doesn't necessarily validate that every internal anchor resolves.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 03a2da8089
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## 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). |
There was a problem hiding this comment.
This says mogplex login writes credentials to the OS keyring, but the repo’s canonical CLI docs state that browser/provider credentials are stored in ~/.mogplex/auth.json (see content/docs/cli/commands/login.mdx and content/docs/cli/guides/authentication.mdx). In practice, users troubleshooting auth or auditing token storage will be sent to the wrong place, and this contradiction is repeated in content/docs/extend/skills.mdx.
Useful? React with 👍 / 👎.
1 participant
Adds a top-level Extend section covering the outbound direction — how external agents (Claude Code, Cursor, Claude Agent SDK, opencode) reach a user's Mogplex workspace — and clarifies it vs. the existing inbound-MCP story in Settings → Connections.
What's new
/extend— hub page with a Skills-vs-MCP decision table and a clear "which path to use today" matrix./extend/mcp-server— preview-state page documenting the planned Mogplex MCP server: remote Streamable HTTP, OAuth 2.1 + PKCE with Dynamic Client Registration (no pasted tokens), v1 tool surface (tools/agents/skills/memories), scopes, and client install snippets for when it ships./extend/skills— positions Skills as today's substitute, with a side-by-side comparison table against the MCP server and a pointer to the canonical reference under/cli/skills.Cross-links added
docs/meta.json+ get-started cards now include Extend.cli/skills/index.mdxlinks out to the Skills-vs-MCP comparison.web/settings.mdxConnections section gets a Callout clarifying that page is inbound MCP, with a pointer to Extend for the outbound direction.Test plan
pnpm lintpnpm types:checkpnpm build— 168 static pages; new/extend/*routes generated (preview andllms.mdxincluded)extend/mcp-server— explicit "preview / not live" framing so readers don't try the endpoints yet