Skip to main content

Honen speaks MCP.

Use Honen from your AI assistant. Search approved knowledge, create courses, assessments, or Atoms, preview learning content in supported clients, and share a link when it is ready.

Streamable HTTPOAuthNo API key
MCP endpointhttps://honen.com/api/mcp/mcp

Paste this into your client’s MCP settings. A browser window opens, you sign in to Honen and click Allow, and the tools appear. Nothing is shared until you approve it.

The complete Honen reference.

Read the platform overview, feature guides, and integration reference as Markdown. Use the index to find a topic or read the complete reference in one file.

/llms-full.txtRecommendedEvery topic guide in one file, with a table of contents. Search the full reference or give it to your AI assistant./llms.txtThe index: four sections linking each topic document separately, if you would rather fetch only the one you need.

Add it to your editor.

These open the client you already have installed and hand it the endpoint. You still review and approve the server before anything runs.

Cursor

Opens Cursor and pre-fills the server for you to approve.

Add to CursorDocs
VS Code

Adds Honen to your user-profile mcp.json via Copilot Chat.

Add to VS CodeDocs
VS Code Insiders

Same install, against the Insiders build.

Add to InsidersDocs
LM Studio

Adds Honen as a remote MCP server in LM Studio.

Add to LM Studio

Or paste the URL.

Clients without an install link take the same endpoint. Two commands and one settings screen cover the rest.

Claude CodeDocs

One command, then /mcp in the session to authenticate.

Terminal
claude mcp add --transport http honen https://honen.com/api/mcp/mcp
Claude apps and claude.aiDocs

Settings → Connectors → Add custom connector, then paste the endpoint. Claude walks you through sign-in.

ChatGPT

Settings → Connectors → add a custom connector and paste the endpoint. Availability depends on your plan and on whether your workspace admin has allowed custom connectors.

Windsurf, Zed, or anything else

Drop this into the client’s MCP config file. The key name is yours to choose.

JSON
{
  "mcpServers": {
    "honen": {
      "type": "http",
      "url": "https://honen.com/api/mcp/mcp"
    }
  }
}

Your workspace permissions apply.

The connection authenticates as you, over OAuth, and every tool call is checked against your existing workspace permissions. There is no separate API key to leak, and a connected agent cannot read a course, a learner record, or a Knowledge Base document you could not already open yourself. Workspace admins can see and revoke connections at any time.

Signed in? Set it up from your dashboard