DevHoardDocs
TermsPrivacyHomeOpen app

guides · mcp · cursor

MCP in Cursor

Updated Sun Aug 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Connect Cursor to DevHoard MCP

Point Cursor at DevHoard over Streamable HTTP using a Bearer API key from Settings → API keys.

Production URL (prefer www):

https://www.devhoard.me/api/mcp

Keys are stored hashed. The raw token is shown once at creation — copy it somewhere safe, then revoke if it leaks.

Create a key

  1. Sign in at devhoard.me
  2. Open Settings → API keys
  3. Prefer read + propose for agents that should capture without editing existing items; use full write only when needed
  4. Copy dh_<prefix>_<secret> into Cursor’s MCP config — never commit it to git

Cursor config (Streamable HTTP)

{
  "mcpServers": {
    "devhoard": {
      "url": "https://www.devhoard.me/api/mcp",
      "headers": {
        "Authorization": "Bearer dh_YOUR_PREFIX_YOUR_SECRET"
      }
    }
  }
}

Exact JSON shape can vary slightly by Cursor version — keep the URL and Bearer header.

What agents can do

Typical tools: search, get item, create/update (scope permitting), list prompts/resources, list items. New captures land in the Hoard MCP Inbox at /app/inbox until you Keep or Dismiss. Provenance (MCP / pack / import / CLI) is stored on items. SECRET content stays off-limits to MCP.

Smoke check

After connecting: list tools, search_items with a known title, create a small NOTE with a propose/write key, confirm it appears in Hoard MCP Inbox (/app/inbox).

Related

overview · vault-items · item-types