Skip to content

[created by claude] Split the Claude and ChatGPT page into a landing page, setup pages, and a connector reference - #1168

Closed
InlinePizza wants to merge 9 commits into
mainfrom
fixup-mcp-page
Closed

InlinePizza wants to merge 9 commits into
mainfrom
fixup-mcp-page

Conversation

@InlinePizza

Copy link
Copy Markdown
Contributor

Summary

This PR splits the Claude and ChatGPT page so each reader gets one page that does their job. A Claude user and a ChatGPT user never need each other's setup, and only Owners and reviewers need the server and tool details.

Page URL Purpose
Use Promptless from Claude or ChatGPT /docs/for-docs/work-the-queue/claude-and-chatgpt (unchanged) Landing page: what you can do from a chat, and which page to go to next
Connect Promptless to Claude .../claude-and-chatgpt/claude Takes a Claude user (web or desktop) from no connection to a tested connector
Connect Promptless to ChatGPT .../claude-and-chatgpt/chatgpt The same for ChatGPT
Promptless connector reference .../claude-and-chatgpt/connector-reference What a connection can access, server details, and the 20 tools

After this merges: update the Claude directory submission to link to .../claude-and-chatgpt/claude.

What changed in the content

  • Claude setup now leads with the connectors directory, which listed Promptless on 2026-10-14. It has separate steps for Owners and members and covers the Request button. Adding Promptless as a custom connector is now a short fallback that links to Anthropic's steps.
  • Vendor UI is current as of 2026-10-16.
    • Claude tool permissions are now Always allow / Needs approval / Blocked.
    • Claude has separate Disconnect and Remove actions, and a Reconnect button.
    • ChatGPT setup now goes through Plugins > Add custom MCP server. Developer mode stays as a note for accounts with the earlier layout.
  • The approval steps use the page's real labels: Returns to, Organization, Your role, and Create organization and authorize as {email}. They match promptless-dashboard/src/app/mcp/authorize.
  • The tool table now lists message_promptless_support, so all 20 tools on /mcp/with-direct-edits appear (runtime/mcp/profiles.py). The reference page also gains an "Approval request" row: requests expire after 30 minutes.
  • Each setup page has its own approval steps, test prompts, and troubleshooting. That text is written out on both pages rather than imported from one shared file, because the .md copies of pages (which agents read) drop imported MDX. Comments on both pages mark the text that must stay in sync.
  • Front matter carries the page brief: purpose, audience, out_of_scope, depends_on_external_ui, and last_verified.

The token lifetimes, approval expiry, membership checks, and tool annotations were checked against runtime origin/main on 2026-10-16.

Needs verification

These are hidden TODO(verify) comments in the pages. The ChatGPT help pages returned 403, so the ChatGPT steps come from search summaries of OpenAI's help article.

  • The Claude directory listing uses https://api.gopromptless.ai/mcp/with-direct-edits.
  • Directory connectors are available on the Claude Free plan.
  • Whether Promptless supports Claude's "Use Claude's published identity" (CIMD). The runtime advertises dynamic client registration only.
  • Owners can block individual tools in Organization settings > Connectors.
  • The labels in the ChatGPT Plugins steps, and whether the Promptless tab opens at Create as a plugin or at install.
  • Whether ChatGPT Plus can add custom MCP servers.
  • The ChatGPT reconnect and disconnect labels.

Collateral changes

  • astro.config.mjs: the "Work the queue" group is now listed page by page, so the new folder shows as a "Claude & ChatGPT" group (Overview, Claude, ChatGPT, Connector reference). Without this, the group would show the raw folder name.
  • connect/triggers/mcp.mdx: updated the link text to the landing page's new title.
  • Added OG images and manifest entries for the four pages.
  • No redirects, because the existing URL still serves the landing page.

Checks

  • Vale, remark-lint, and docmeta pass.
  • npm run build passes.
  • All links and anchors on the four built pages resolve.
  • npm run test:smoke passes 27 of 28. The one failure, agent score landing renders its form…, has been failing since Trim the Agent Score hero and scan progress copy #1159 changed the Agent Score hero copy, so it isn't caused by this PR.

Out of scope, worth fixing

  • The MCP triggers page: its Claude section uses /mcp and the old custom-connector steps, and its tool counts are out of date.
  • The consent page tells web-app users to "run the connect command in your editor". The new troubleshooting sections tell readers to ignore that wording.
  • Open PR docs: Add a dedicated Promptless MCP server page #1109 edits the old intro of this page. It will need a rebase after this merges.

…p and reference comes last

Moves sections without rewording: Data access before the setup steps, Test the
connection right after approval, and Server details and Tools under a closing
Reference section.
…at app

- Open with what the reader can do and who the page is for, and route editor
  users to MCP triggers. Cut the list of other review surfaces.
- Lead Claude setup with the connectors directory (listed 2026-10-14), with
  separate steps for Owners and members and a custom-connector fallback.
- Update Claude tool-permission labels and the ChatGPT Plugins flow. Mark the
  vendor UI that couldn't be confirmed with TODO(verify) comments.
- Use the approval page's own labels (Returns to, Organization, Your role) and
  document the create-organization path.
- Add message_promptless_support to the tool table (20 tools on the chat URL).
- Move the wrong-URL fix into Troubleshooting, and add next steps.
- Carry the page brief (purpose, audience, scope) in frontmatter.
… pages

The existing URL becomes a short landing page that routes to:
- Connect Promptless to Claude (claude-and-chatgpt/claude)
- Connect Promptless to ChatGPT (claude-and-chatgpt/chatgpt)
- Promptless connector reference (claude-and-chatgpt/connector-reference):
  access, server details, and tools

Each setup page carries its own approval steps, test prompts, and
troubleshooting so a reader never has to jump pages. The shared text is
inlined, not imported, because the .md twins drop imported MDX.

Work the queue is now enumerated in astro.config.mjs so the new subfolder
gets a 'Claude & ChatGPT' group label.
@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
promptless-docs Ready Ready Preview Oct 20, 2026 5:47pm UTC

Request Review

@promptless promptless Bot changed the title docs: Split the Claude and ChatGPT page into a landing page, setup pages, and a connector reference [created by claude] Split the Claude and ChatGPT page into a landing page, setup pages, and a connector reference Oct 16, 2026
Resolve the frontmatter conflict on the Claude and ChatGPT landing page by
keeping the landing-page title, description, type, and sidebar and adopting
main's manni metadata. Add ids to the three new Claude and ChatGPT pages and
restamp derived fields so manni meta validate passes.
@promptless

promptless Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

I noticed that some CI checks failed for this PR. I'm investigating whether the failures are caused by this suggestion. If they're unrelated or pre-existing, I'll leave this suggestion unchanged and create a separate suggestion if a standalone docs fix is needed.

# Conflicts:
#	src/content/docs/docs/for-docs/connect/triggers/mcp.mdx
#	src/content/docs/docs/for-docs/work-the-queue/claude-and-chatgpt.mdx
@promptless

promptless Bot commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Dashboard comment by isaiah@gopromptless.ai:

Closed this suggestion.

This branch was successfully deployed

1 active deployment
Preview — 1e41ab08 Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant