Skip to content

docs: add Caffeine as an entry point and document its MCP server - #416

Open
raymondk wants to merge 1 commit into
mainfrom
docs/caffeine-entry-points
Open

docs: add Caffeine as an entry point and document its MCP server#416
raymondk wants to merge 1 commit into
mainfrom
docs/caffeine-entry-points

Conversation

@raymondk

@raymondk raymondk commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Choose your path: new "Ship an app without a toolchain" path positioning Caffeine as the no-install entry point alongside the icp-cli quickstart. States plainly that Caffeine's cloud agent builds and hosts the app and that publishing to a live URL happens in the Caffeine web app.
  • AI coding agents: new "Drive Caffeine from your agent" section covering the hosted Caffeine MCP server: what it does and does not do (drives Caffeine's cloud agent, never touches local code or ships source to the AI tool), the local-CLI workflow for desktop agents, the one-line Claude Code setup, and a pointer to the caffeine-app skill. An alpha note links to Caffeine's setup article for the other clients and troubleshooting.
  • Developer tools: new "AI app builder" category with a Caffeine entry next to ICP Ninja.

Structural decisions

  • No new page. Caffeine owns its own help center and verbal system, so these docs link out rather than duplicate, and a standalone page would drift as the MCP alpha changes. The three touched pages are where a developer already lands for each question (how do I start, I use an agent, what tools exist).
  • The Claude Code command and server URL are inlined rather than only linked because help.caffeine.ai returns 403 to non-browser clients, so agents reading /llms.txt cannot follow the link.
  • The MCP tool table is deliberately not reproduced: the article marks the tool surface as alpha and subject to change.

Verified

  • Content checked against the help center article (updated 2026-06-04, fetched via the Zendesk API) and the caffeine-app skill on skills.internetcomputer.org.
  • @caffeineai/cli resolves on the npm registry; all new internal links and anchors render in the built HTML.
  • npm run build passes.

@raymondk
docs: add Caffeine as an entry point and document its MCP server
d325039 
Add a "Ship an app without a toolchain" path to Choose your path, a
"Drive Caffeine from your agent" section to the AI coding agents guide
covering the hosted Caffeine MCP server, and a Caffeine entry in the
Developer tools inventory next to ICP Ninja.
@raymondk
raymondk requested a review from a team as a code owner October 2, 2026 13:58
@github-actions

github-actions Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Here's your preview: https://keluh-vqaaa-aaaam-ai7wa-cai.icp0.io

marc0olo
marc0olo approved these changes Oct 2, 2026
View reviewed changes

@marc0olo marc0olo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raymondk you might also want to update the caffeine-app skill where the original skill lives here: https://github.com/caffeinelabs/caffeine-cli/tree/main/skills/caffeine-app

I didn't yet set up an upstream check because its a private repo. in any case the current caffeine-app skill requires some update if I recall correctly.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@marc0olo marc0olo marc0olo approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@raymondk @marc0olo