Computeback vs Obsidian MCP Server

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

Computeback logoComputebackKnowledge & Memory · Local subprocess (stdio)Agent marketplace: earn $NOMD on B2B work, spend on compute/voice/memory capabilities.51GoodAuth: not declaredObsidian MCP Server logoObsidian MCP ServerKnowledge & Memory · Local subprocess (stdio)MCP server for Obsidian vaults — read, write, search, and edit notes via the Local REST API plugin.65GreatAuth: not declared

Verdict: choose Computeback for knowledge & memory work as a local process; choose Obsidian MCP Server for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Computeback logoChoose Computeback when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_products, get_product, get_categories.
Explore Computeback

Obsidian MCP Server logoChoose Obsidian MCP Server when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: OBSIDIAN_API_KEY.
  • You want tools like obsidian_get_note, obsidian_list_notes, obsidian_list_tags.
Explore Obsidian MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecComputeback logoComputebackObsidian MCP Server logoObsidian MCP Server
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal51/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedOBSIDIAN_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars0701
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools1614

Tools & capabilities

Computeback tools 16

  • search_productsfilter / search the catalog
  • get_productfull product info ($NOMD price, vendor, fulfillment)
  • get_categorieslist 25+ capability categories
  • check_balanceagent's $NOMD balance on Base L2
  • create_orderpurchase a product (burns $NOMD)
  • get_ordersagent's order history
  • get_recommendationspersonalized picks
  • buy_nomdlink to Treasury Sale Vault (USDC → $NOMD)
  • list_my_inboxopen offers, assignments, bids
  • place_bidbid on open_bidding / reverse_auction offers
  • withdraw_bidretract a pending bid
  • fetch_urlfetch public URLs for outreach research
  • +4 more on the listing page

Obsidian MCP Server tools 14

  • obsidian_get_noteRead a note as raw content, full structured form, document map, or a single section
  • obsidian_list_notesList notes and folders under a vault path, recursively, with extension and name filters
  • obsidian_list_tagsList vault tags with usage counts, most-used first
  • obsidian_search_notesSearch by text, JSONLogic, or BM25-ranked Omnisearch when that plugin is reachable
  • obsidian_write_noteCreate a note, replace one section, or overwrite a whole file with `overwrite: true
  • obsidian_append_to_noteAppend to a note (creating it if missing) or to one heading, block, or frontmatter field
  • obsidian_patch_noteAppend, prepend, or replace against one heading, block reference, or frontmatter field
  • obsidian_replace_in_noteLiteral or regex search-replace inside one note, body-only by default
  • obsidian_manage_frontmatterGet, set, or delete one frontmatter key
  • obsidian_manage_tagsAdd, remove, or list a note's tags in frontmatter, inline, or both
  • obsidian_delete_notePermanently delete a note, optionally after the user confirms (`OBSIDIAN_DELETE_ELICITATION`)
  • obsidian_open_in_uiOpen a file in the Obsidian app, optionally in a new pane
  • +2 more on the listing page

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.

Computeback

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "computeback": {
      "command": "npx",
      "args": [
        "-y",
        "@autonomad1/computeback-mcp"
      ]
    }
  }
}

Obsidian MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "obsidian-mcp-server": {
      "command": "bunx",
      "args": [
        "obsidian-mcp-server@latest"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Computeback is categorized under Knowledge & Memory and uses a local stdio subprocess. Obsidian MCP Server belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Computeback for knowledge & memory work and Obsidian MCP Server for knowledge & memory.

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.

Computeback has no declared pricing — check the project's own site. Obsidian MCP Server 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 computeback and obsidian-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Computeback has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Obsidian MCP Server has 65/100 (Great) with 5 views, 0 installs and 701 GitHub stars.