What kind of documentation does McpDocs serve?
It serves documentation about your Elixir project’s functions and the functions of its dependencies.
@josiahdahl
基本情報
Provide documentation about your Elixir project's functions and functions of dependencies to an LLM through an SSE MCP server.
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
McpDocs is an Elixir library that serves documentation about your Elixir project's functions and its dependencies to an LLM (Large Language Model) through an SSE (Server-Sent Events) MCP (Model Context Protocol) server. It is intended for Elixir developers who want to give AI assistants contextual knowledge of their codebase.
Add {:mcp_docs, github: "josiahdahl/mcp_docs", runtime: false, only: [:test, :dev]} to your mix.exs dependencies. Then run mix mcp_docs.start (optionally with --port <port>, default 9702) to start the SSE server. You can also use iex -S mix mcp_docs.start for manual recompiling. Try it out with npx @modelcontextprotocol/inspector.
It serves documentation about your Elixir project’s functions and the functions of its dependencies.
Run `mix mcp_docs.start`; the SSE server listens by default on port 9702. An LLM client can connect to that endpoint.
The package should be added with `runtime: false` and `only: [:test, :dev]`, meaning it is not needed in production.
It uses Server-Sent Events (SSE) as the MCP transport.
No authentication is mentioned, and automatic recompilation is on the roadmap but not yet implemented.
Shared, serverless, conflict-free memory for AI agents: a multi-machine drop-in for the MCP memory knowledge graph.
Groundwork: company memory for your AI tools. Docs public. Source closed. Public proof needs no account.

The official Semantic-UI-React integration

MCP connector for Snipara, the Project Brain for AI coding agents

Persistent memory for AI agents. Hosted MCP server with capsule-scoped key/value storage, tags, TTL expiration, bulk ops, and RBAC.
コメント