Integrations · Claude Desktop

Halyard for
Claude Desktop.

Chat with your team's knowledge from inside Claude Desktop. One MCP config entry and Claude retrieves from Slack, Notion, GitHub, Drive, and meeting notes — with citations, not hallucinations.

01 · Install

Edit one file.

Claude Desktop reads MCP servers from a local config file. Add Halyard's endpoint, restart Claude, and you're grounded.

claude_desktop_config.json macOS / Windows
{
  "mcpServers": {
    "halyard": {
      "url": "https://mcp.usehalyard.ai",
      "transport": "streamable-http"
    }
  }
}

✓ restart Claude Desktop
✓ authorise Halyard via OAuth on first use
✓ claude can now search, ask teammates, capture knowledge

Config file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows. See the full docs if you prefer the stdio transport or are running Claude Desktop Enterprise.

02 · What Claude Desktop gains

Cited answers.
Not invented ones.

Claude Desktop is great for drafting, planning, summarising. Halyard grounds those responses in what your team already knows — across every source you've connected.

Customer success
Q

"What's our stance on tiered support SLAs?"

→

Standard: 24h response. Premium: 4h. See the support-tiers doc last updated by Priya in Jan.

Support tiers · Notion#customer-success
Sales
Q

"Summarise the last three calls with Acme Corp."

→

Pulled from Granola meeting notes — here are the three most recent, with action items + decisions.

Granola · Acme Corp#sales-acme
Design
Q

"What was decided about gold as the brand accent?"

→

Kept gold after the April brand refresh. See brand-tokens.css + the brand playbook.

Brand playbook · Notionbrand-tokens.css
03 · Why this is a good fit

Desktop chat + org memory.

Claude Desktop is the entry point for people who don't live in a terminal or an IDE — operators, GMs, founders, support leads. Halyard makes their chats grounded in the same knowledge Claude Code sees.

→

No CLI required

Your non-technical teammates get the same MCP-grounded experience as engineers — just in a chat window.

→

One config per workstation

Add Halyard once, it's there for every Claude conversation. Works in Projects, Artifacts, plain chat.

→

Ask teammates without leaving Claude

When Claude hits an unknown, it triggers ask_expert — Halyard pings the right person in Slack, answer streams back into the chat.

Chat with your team's brain.

One config, one OAuth, every Claude Desktop chat starts grounded.