Connect an agent

Point your coding agent at ShepAIrd and it gets the same product as the CLI: search, memory, and brief, without pasting the repo into the prompt.

Two ways to connect

Child process
The editor starts ShepAIrd itself. Use this when the client can launch a command (typical for a local desktop app).
Network
ShepAIrd is already running, and the client connects to an address. Use this when the agent is on another machine, or several clients share one instance.

Start the server

stdio for a child process, HTTP for a URL
shepaird mcp --stdio --profile agent
shepaird mcp --http :8080 --profile agent
shepaird mcp tools --profile agent

mcp tools prints the tools that profile will expose, so you can confirm what the agent will see before you wire the client.

Example: editor config

A local client launching ShepAIrd
{
  "mcpServers": {
    "shepaird": {
      "command": "shepaird",
      "args": ["mcp", "--stdio", "--profile", "agent"]
    }
  }
}

Put shepaird on the PATH the editor uses, save, and restart the client. The next session can search and remember without a paste of the tree.

Which profile

agent
The default set of tools a coding agent should see.
agent-min
A smaller set, when the client wants fewer tools in context.