Learning Resources
katari-lang.dev
MCP server for the Katari programming language that provides documentation search, page reading, package browsing, and onboarding resources.
ENDPOINT 1
https://katari-lang.dev/mcp
MCP server metadata
- Name
- katari-docs-mcp
- Version
- 0.1.0
Known tools 4
read_docRead one Katari documentation page as raw markdown, by the path a search result or the onboarding page map returned (e.g.
Inferred read-onlypackagesBrowse the Katari standard library (prelude) and registry packages, with staged detail.
Inferred read-onlyonboardingStart here if you do not know Katari: an orientation for writing Katari programs — what the language is, its core concepts (agents, effects, escalation, durable execution), and a quickstart — plus links to four complete example projects and the full documentation page map for follow-up reads with "read_doc".
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.katari-docs-mcp]
url = "https://katari-lang.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"katari-docs-mcp": {
"type": "http",
"url": "https://katari-lang.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: katari-docs-mcp
Remote MCP URL: https://katari-lang.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"katari-docs-mcp": {
"url": "https://katari-lang.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"katari-docs-mcp": {
"type": "http",
"url": "https://katari-lang.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "katari-docs-mcp",
"transport": "streamable-http",
"url": "https://katari-lang.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.