Hangarvibe

Reference

Hangar MCP

Connect any MCP client — Claude Code, Claude Desktop, Cursor — to your Hangarvibe workspace. Your agent gets 6 hangar_* tools for projects, tasks, knowledge, and memory.

Quick start (desktop app)

The fastest path: create a key in the dashboard (API keys → Create key — it starts with hg_live_ and is shown only once), paste it in the desktop app under Settings → MCP, click Test connection, then click Connect project in the deck header. That writes a .mcp.json into your project folder (and gitignores it — the file embeds your key). Restart your terminals to pick up the tools.

Connect from any machine

Hangar MCP speaks Streamable-HTTP MCP, so any client that supports remote MCP servers connects with the URL plus your key as a bearer header.

Claude Code
claude mcp add --transport http hangarvibe https://hangarvibe.com/api/mcp \
  --header "Authorization: Bearer hg_live_YOUR_KEY"
Claude Desktop / Cursor (mcpServers config)
{
  "mcpServers": {
    "hangarvibe": {
      "url": "https://hangarvibe.com/api/mcp",
      "headers": {
        "Authorization": "Bearer hg_live_YOUR_KEY"
      }
    }
  }
}

To pin every call to one project, add an X-Hangar-Project header with the project id — or pass a project_id argument on individual tool calls.

The 6 tools

hangar_projectList your projects or create a new one.
hangar_taskList, read, create, and update tasks — and attach knowledge to a task.
hangar_agentList, read, and remove the agents registered in your workspace.
hangar_knowledgeSearch, read, and add project knowledge. Searches are metered.
hangar_memorySearch, read, add, and link memory notes. Searches are metered.
hangar_apiCheck who the key belongs to, your credit balance, and recent usage.

Keys, credits, and limits

Keys come in two flavors: hg_live_ for real work and hg_test_ for testing. A key can be restricted to specific projects and scopes when you create it. Never commit a key — the desktop Connect-project flow gitignores the file that holds it for you.

Searches with hangar_knowledge and hangar_memory are metered and draw from your plan’s credits. An immediate retry of the same search is not billed twice. Requests are rate-limited per key.

Related