Monitor vs Obsidian MCP Secure

A side-by-side look at the Monitor and Obsidian MCP Secure MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Monitor logoMonitorMonitoring · Local subprocess (stdio)Valkey-first observability with Redis compatibility. Query real-time metrics, analyze slow commands, detect hot keys, and investigate performance issues directly from AI coding assistants.64GoodAuth: api key requiredObsidian MCP Secure logoObsidian MCP SecureMonitoring · Local subprocess (stdio)Secure MCP server for Obsidian with OWASP Top 10 controls and full audit logging.56GoodAuth: not declared

Verdict: choose Monitor for monitoring work as a local process; choose Obsidian MCP Secure for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Monitor logoChoose Monitor when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Monitor

Obsidian MCP Secure logoChoose Obsidian MCP Secure when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: OBSIDIAN_API_KEY, OBSIDIAN_HOST, OBSIDIAN_PORT, LOG_DIR.
  • You want tools like read_note, list_notes, create_note.
Explore Obsidian MCP Secure

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMonitor logoMonitorObsidian MCP Secure logoObsidian MCP Secure
CategoryMonitoringMonitoring
Quality signal64/100 · Good56/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreemiumNot declared
Required env varsNone listedOBSIDIAN_API_KEYOBSIDIAN_HOSTOBSIDIAN_PORTLOG_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars1,3090
Directory activity 5 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed9

Tools & capabilities

Monitor tools

No tool names declared yet. Check the project README from the listing page.

Obsidian MCP Secure tools 9

  • read_noteLê o conteúdo de uma nota do Obsidian pelo caminho
  • list_notesLista arquivos e pastas do vault ou de um diretório específico
  • create_noteCria uma nova nota no Obsidian
  • edit_noteEdita o conteúdo de uma nota existente (substitui o conteúdo inteiro)
  • delete_noteDeleta uma nota do vault. ATENÇÃO: ação irreversível.
  • search_notesBusca notas por conteúdo ou tag no vault
  • find_note_by_nameEncontra notas pelo nome (busca parcial, insensível a maiúsculas). Útil quando o caminho exato não é conhecido.
  • list_tagsLista todas as tags usadas no vault com contagem de ocorrências
  • create_backlinksAdiciona wikilinks [[NomeDaNota]] na seção '## Relacionadas' da nota source. Cria a seção se não existir.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Monitor

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "betterdb-inc-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/monitor"
      ]
    }
  }
}

Obsidian MCP Secure

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "obsidian-mcp-secure": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-mcp-secure"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE",
        "OBSIDIAN_HOST": "YOUR_OBSIDIAN_HOST_HERE",
        "OBSIDIAN_PORT": "YOUR_OBSIDIAN_PORT_HERE",
        "LOG_DIR": "YOUR_LOG_DIR_HERE"
      }
    }
  }
}

Frequently asked questions

Monitor is categorized under Monitoring and uses a local stdio subprocess. Obsidian MCP Secure belongs to Monitoring and uses a local stdio subprocess. Pick Monitor for monitoring work and Obsidian MCP Secure for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Monitor is listed as freemium — a free tier with paid plans. Auth: api key required. Obsidian MCP Secure has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add betterdb-inc-monitor and obsidian-mcp-secure as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Monitor has a quality signal of 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars. Obsidian MCP Secure has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.