Connecting AI coding agents to the TinyMCE documentation
An AI coding agent works from its training data unless it is given something better. This page describes four ways to put the current TinyMCE documentation in front of an agent. They are alternatives rather than steps, and any of them can be used together. Each applies to any TinyMCE installation, whether it is served from the Tiny Cloud or self-hosted.
-
TinyMCE documentation MCP server — a hosted Model Context Protocol (MCP) server that serves this documentation and nothing else. Suits any agent that supports MCP.
-
Context7 — a general-purpose documentation MCP server that also indexes the TinyMCE documentation. Suits an agent already using Context7 for other libraries.
-
Markdown pages — every documentation page is also published as markdown at its own URL. Suits an agent without MCP support, or a prompt that already names the page.
-
llms.txtfiles — two plain text summaries of the whole documentation set, for an agent that accepts a single bulk reference.
| To add TinyMCE to a project with an AI coding agent, see the Tiny Cloud AI quick start guide. |
Connect the TinyMCE documentation MCP server
The TinyMCE documentation MCP server is hosted by Tiny and serves this documentation set alone. It exposes semantic search across the published pages, returning relevant extracts with links to their source. Any client that supports MCP over streamable HTTP can connect to it.
Endpoint: https://tinymcedocs.mcp.kapa.ai
Authentication: The server is protected by OAuth and requires a one-time sign-in. The first time the agent calls the server, a browser window opens to complete sign-in, after which the agent stores the resulting token. If no sign-in prompt appears, trigger authentication from the agent’s own MCP configuration, as described in the entry for that agent below.
|
Each agent reads its own configuration file, and the files are not interchangeable. Claude Code reads |
Install from the documentation site
Every page of this documentation includes an Ask AI widget. Open the widget and select Use MCP in the modal header to open the Connect to AI Tools menu, which provides copy-to-clipboard install commands, one-click installs for supported editors, and the raw server URL.
The entries below describe the equivalent manual configuration.
Manual configuration by agent
Each agent below is configured independently. Expand the entry for the agent in use.
Claude Code
If no sign-in prompt appears, run /mcp, select the server, and then select Authenticate.
claude mcp add --transport http --scope project tinymce-docs https://tinymcedocs.mcp.kapa.ai
To configure the server manually, add it to .mcp.json:
{
"mcpServers": {
"tinymce-docs": {
"type": "http",
"url": "https://tinymcedocs.mcp.kapa.ai"
}
}
}
Cursor
Add the server to .cursor/mcp.json:
{
"mcpServers": {
"tinymce-docs": {
"url": "https://tinymcedocs.mcp.kapa.ai"
}
}
}
Codex
codex mcp add tinymce-docs --url https://tinymcedocs.mcp.kapa.ai
To configure the server manually, add it to ~/.codex/config.toml:
[mcp_servers.tinymce-docs]
url = "https://tinymcedocs.mcp.kapa.ai"
startup_timeout_sec = 20
tool_timeout_sec = 60
enabled = true
Visual Studio Code
Add the server to .vscode/mcp.json:
{
"servers": {
"tinymce-docs": {
"type": "http",
"url": "https://tinymcedocs.mcp.kapa.ai"
}
}
}
OpenCode
Add the server to opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tinymce-docs": {
"type": "remote",
"url": "https://tinymcedocs.mcp.kapa.ai",
"enabled": true
}
}
}
Other agents
For any other agent, point its MCP client at the streamable HTTP endpoint and complete the sign-in described above. Agents that accept a remote MCP server without a dedicated configuration file, such as Claude and ChatGPT, can connect using the endpoint directly:
https://tinymcedocs.mcp.kapa.ai
Connect Context7
Context7 is a general-purpose documentation MCP server that serves version-specific library documentation for many projects, including TinyMCE, from a single server. An agent already using Context7 for other libraries can reach the TinyMCE documentation without adding a second server.
Library: tinymce/docs at context7.com/tinymce/tinymce-docs
Configure Context7 following its own installation instructions, then reference the tinymce/docs library in prompts so the agent resolves TinyMCE questions against it.
Read the documentation as markdown
Agents can read the documentation efficiently without the MCP server. Every documentation page is also published as markdown, which is more token-efficient than the rendered HTML page. Append index.md to any documentation page URL to retrieve it:
https://www.tiny.cloud/docs/tinymce/latest/basic-setup/index.md
Markdown is available for every documented version of TinyMCE, not only the latest release. Replace latest with a version segment to retrieve the markdown for an earlier version:
https://www.tiny.cloud/docs/tinymce/7/basic-setup/index.md
The current major version is always served from latest. A request for that version by number, such as /docs/tinymce/{productmajorversion}/basic-setup/index.md, redirects to its latest address, so an agent retrieving markdown by version number needs to follow redirects. Earlier versions are served directly.
Each page also includes a Copy Markdown button next to the page title, which copies the markdown URL of the current page to the clipboard for pasting into an agent prompt.
llms.txt files
Two plain text files summarize the documentation set for agents that accept a single bulk reference. Both files index the latest release:
| File | Contents |
|---|---|
A concise overview of TinyMCE, with key links and code examples. |
|
A full index of the documentation pages and their URLs. |
Feedback
Report inaccurate or outdated documentation by opening an issue in the tinymce-docs GitHub repository. Agents are encouraged to file these when the documentation contradicts what actually worked.