Documentation

MCP

The endpoint, the tools and resources it publishes, and how authorization works.

Framulus is a remote MCP server. One endpoint serves every client: a published app, a custom connector and a local CLI present the same kind of token, call the same tools and take the same path into the document.

https://<your Framulus>/api/agent/mcp

Resources

An agent discovers Framulus for itself rather than being handed a large prompt. framulus://capabilities and framulus://markup-guide describe the software and are answered by the server. framulus://document, framulus://design-system and framulus://templates describe the open document and are answered by the editor tab through a read tool.

Authorization

A client registers itself, sends you to a Framulus consent screen, and receives a grant. The grant is for your account rather than for one project: which document a call lands in is resolved per call, from the editor session you currently have open.

Two editors open is a refusal

If more than one Framulus editor is open, there is no single document to act on and the call is refused with a message saying so. Guessing would change a deck nobody is looking at.