Obsidianki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_flashcardsA | Generate flashcards using obsidianki. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| instructions | Instructions for using the flashcard generation tool |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
The single tool uses a clear verb_noun pattern ('generate_flashcards'), which is consistent within the server.
The server has only one tool, which is the bare minimum. For a single-purpose server focused on generating flashcards, this is borderline but not excessive.
The tool only supports generation. There are no tools for viewing, updating, or deleting flashcards, creating significant gaps for any workflow beyond initial generation.