Skip to main content
Glama

Obsidian MCP Server

Apache 2.0
338
222
  • Apple
  • Linux
commandMethods.ts1.39 kB
/** * @module CommandMethods * @description * Methods for interacting with Obsidian commands via the REST API. */ import { RequestContext } from "../../../utils/index.js"; import { ObsidianCommand, CommandListResponse, RequestFunction, } from "../types.js"; /** * Executes a registered Obsidian command by its ID. * @param _request - The internal request function from the service instance. * @param commandId - The ID of the command (e.g., "app:go-back"). * @param context - Request context. * @returns {Promise<void>} Resolves on success (204 No Content). */ export async function executeCommand( _request: RequestFunction, commandId: string, context: RequestContext, ): Promise<void> { await _request<void>( { method: "POST", url: `/commands/${encodeURIComponent(commandId)}/`, }, context, "executeCommand", ); } /** * Lists all available Obsidian commands. * @param _request - The internal request function from the service instance. * @param context - Request context. * @returns A list of available commands. */ export async function listCommands( _request: RequestFunction, context: RequestContext, ): Promise<ObsidianCommand[]> { const response = await _request<CommandListResponse>( { method: "GET", url: "/commands/", }, context, "listCommands", ); return response.commands; }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyanheads/obsidian-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server