Claude Code
This connects Claude Code to the Halyard MCP server so the agent can search knowledge, ask experts, and capture answers. For developers wiring up a single client.
Configure
Section titled “Configure”There are two ways to register Halyard. The plugin also installs Halyard’s prompt rules; the direct registration is the minimal MCP-only path.
With the plugin
Section titled “With the plugin”Add Halyard’s marketplace and install the plugin from inside Claude Code:
/plugin marketplace add halyard-labs/claude-plugin-marketplace/plugin install halyard@halyard-labsUsing the Claude desktop app (Cowork) instead of the terminal? Add the same plugin through the UI — see Claude desktop app.
Manual config
Section titled “Manual config”Register the remote server directly:
claude mcp add --transport http halyard https://mcp.usehalyard.aiRoll it out across a repo
Section titled “Roll it out across a repo”To make Halyard available to everyone who opens a repo, commit a .claude/settings.json that enables the plugin and declares the marketplace it comes from:
{ "enabledPlugins": ["halyard@halyard-labs"], "extraKnownMarketplaces": { "halyard-labs": { "source": { "source": "github", "repo": "halyard-labs/claude-plugin-marketplace" } } }}Authorize
Section titled “Authorize”The first time the agent calls a Halyard tool, Claude Code opens a browser to authorize against your Halyard account. Approve it once; the bearer token is then attached to every request.
Verify
Section titled “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. If the tools do not appear, see Troubleshooting.