Skip to main content
Glama
UwUGreed

Obsidian MCP Wrapper

by UwUGreed

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PF_INDEX_URLYesURL of the pf-index HTTP service (e.g., http://127.0.0.1:8765)
PF_INDEX_TOKENYesBearer token for authenticating with the pf-index service

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

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vault_searchD

vault_search

strategy_searchD

strategy_search

find_noteD

find_note

get_note_summaryD

get_note_summary

get_entity_contextD

get_entity_context

search_tablesD

search_tables

read_sectionD

read_section

expand_contextD

expand_context

get_full_profileD

get_full_profile

advisory_contextD

advisory_context

vault_statsD

vault_stats

append_human_noteD

append_human_note

remove_noteD

remove_note

Prompts

Interactive templates invoked by user choice

NameDescription
pf_vault_usage_rulesOperational rules for safe PF vault retrieval and memory writes

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.8/5.0

Scored across 13 tools

Disambiguation2/5

Multiple tools overlap in purpose: vault_search, strategy_search, find_note, and search_tables all appear to perform search-like operations with unclear distinctions. Similarly, get_entity_context, get_full_profile, and advisory_context all seem to provide contextual or profile information, making it difficult for an agent to choose the right tool.

Naming Consistency3/5

Most tools follow a verb_noun pattern (find_note, get_note_summary, read_section), but vault_search and advisory_context break this convention, and search_tables mixes the order. The inconsistency is moderate, not chaotic, but noticeable.

Tool Count5/5

13 tools is well within the typical 3-15 range and seems appropriately scoped for an Obsidian wrapper covering search, retrieval, and basic note management. The number does not feel excessive or thin.

Completeness3/5

The tool set covers search and read operations comprehensively, but lacks an explicit update or edit tool. append_human_note may create or append, but there is no clear mechanism to modify existing notes, which leaves a notable gap for a note management server.

Maintenance

ActivityInactive
ResponsivenessNo issues