ObsidianUI MCP Server Documentation

Connect a local coding agent to ObsidianUI component resources through the repository's stdio MCP server.

A new direction for ObsidianUI

Now it’s time to be different. Everyone on the internet has already used ready-made components, from images to the smallest details. Atharv (@athrix_codes on X) is taking a big step to build a next-level UI library, because he knows Claude, Gemini, Codex, and any AI can create components in a few minutes. Thank you for supporting us through every moment, guys! We’re going big. Stay tuned!

Run the local MCP server

The repository includes an MCP server in scripts/mcp-server.ts. It uses stdio transport and exposes read-only resources. This documentation URL is not a hosted HTTP MCP endpoint.

Clone the repository, install its dependencies, and generate the component registry. Configure your MCP client to launch npm run mcp with this checkout as its working directory.

git clone https://github.com/Atharvsinh-codez/ObsidianUI.git
cd ObsidianUI
npm ci
npm run registry:build
npm run mcp

MCP server source

Read component resources

Use MCP resources/list to discover available components. Then use resources/read with a returned URI, such as obsidian://hover-img. The resource returns the same application/json registry item used by HTTP installation, including all source and supporting files.

The server exposes resources, not code-execution or file-writing tools. Your coding agent applies the downloaded files in your project with your normal approval and review settings.