Other MCP clients

Any MCP client that speaks HTTP can connect to Halyard. Use the same server block everywhere; only the file location and format differ per client. For developers wiring up a client that does not have its own page.

The shared server block:

{ "type": "http", "url": "https://mcp.usehalyard.ai" }

Tip

Prefer the client’s own UI for adding MCP servers when it has one — it handles the config format and the OAuth handshake for you. Edit the files below only when there is no UI path.

Config file locations

Claude Desktop

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Windsurf

• ~/.codeium/windsurf/mcp_config.json

Authorize

On its first call to a Halyard tool, the client opens a browser to authorize against your Halyard account. Approve it once; the bearer token is then attached to every request.

Clients discover how to authorize from the OAuth metadata Halyard publishes at /.well-known/oauth-protected-resource, which points them at the authorization server https://api.usehalyard.ai. You do not configure these by hand — a spec-compliant MCP client reads them automatically.

Verify

Ask the agent to identify you and run a search:

Use Halyard to tell me who I am, then search the knowledge base for our most recent decision.

Expect a whoami call returning your user and organization, followed by a search_knowledge call. For transport and OAuth details, see the MCP server reference. If the tools do not appear, see Troubleshooting.