WorkBuddy
Let your agent help with setup or add a connector manually.
Configure this client in Quick Start.
Before you start
Send the instructions below to WorkBuddy for help with setup, or edit ~/.workbuddy/mcp.json manually. Complete browser authorization yourself.
See Authentication and API Keys for credential options. Merge only the peoplerouter entry into an existing configuration; do not overwrite other settings.
Set up the connection
Recommended: copy these instructions into a WorkBuddy task. WorkBuddy can help configure the connection; you complete browser authorization.
Connect PeopleRouter in WorkBuddy and automate the configuration where possible.
Check the installed version and ~/.workbuddy/mcp.json. Back up an existing file and merge only mcpServers.peoplerouter, preserving other servers and settings. Create the directory and file if absent. Use:
{
"mcpServers": {
"peoplerouter": {
"type": "streamableHttp",
"url": "https://mcp.peoplerouter.ai"
}
}
}
Use WorkBuddy's built-in OAuth. Do not add a placeholder Authorization header or ask me to create an API key. Wait for me to sign in and authorize DINQ in the browser.
If sandbox restrictions block configuration or authorization through file, network or browser callback access, request the necessary permissions through the current agent's approval mechanism. Where outside-sandbox execution is supported, run the operation only after approval. I will complete browser authorization. Do not repeatedly retry in the same restricted environment, disable the sandbox or bypass approvals. If the environment cannot request permission, give me the exact steps to perform in my local terminal or app UI.
Try reloading the connection. If I must act, guide me through the current Experts / Skills / Connectors area → Connectors → Custom connector, rather than the old Plugins → MCP Servers menu. If the UI differs or authentication fails, report the specific error and required action. Confirm success only after the tools load and capabilities succeeds.Or configure manually: open Experts / Skills / Connectors → Connectors → Custom connector. Labels vary by version. The user-wide file is ~/.workbuddy/mcp.json; merge this entry without replacing other servers. See the official connector guide.
{
"mcpServers": {
"peoplerouter": {
"type": "streamableHttp",
"url": "https://mcp.peoplerouter.ai"
}
}
}Save and connect, then sign in to DINQ and approve access in the browser. OAuth is supported by WorkBuddy's official connector specification; no API key is required for this configuration. Confirm the tools load and capabilities succeeds. If needed, reconnect or start a new task. WorkBuddy 5.5.2 end-to-end sign-in has not been independently tested here.
Check the connection
Once the client has loaded the PeopleRouter tools, send the request below. Inspect capabilities before running a people search.
Use PeopleRouter to list the available capabilities and explain which tools can help find the contributors to a GitHub repository. Do not run a search yet.After connecting, continue to Using tools. For authentication or tool errors, read Troubleshooting and inspect the client's actual error message.