BuildYourWolfpack
com.buildyourwolfpackPublished by buildyourwolfpack.comv1.0.0Updated Oct 25, 2026
Roast-to-order coffee with a game built in: missions, Pack Points, and your own wolf pack.
Overview
A remote MCP endpoint for BuildYourWolfpack, a roast-to-order coffee service with a game layer of missions, Pack Points and a wolf pack.
- What you can do
- The manifest lists no tools, so the exact actions are not documented. The description presents the service as roast-to-order coffee with a game built in, covering missions, Pack Points and a user's own wolf pack. Access is tied to a BuildYourWolfpack game account, so any assistant use would relate to that account and its game activity.
- When to use it
- Consider it only if you already have a BuildYourWolfpack account and want an assistant connected to that coffee-and-game service. Without a published tool list, it is hard to judge in advance what the assistant could actually do.
- Requirements
- A remote streamable HTTP endpoint at the provider's hosted address. Authentication is required via an Authorization header carrying a per-account API key as a Bearer token; keys are issued with a BuildYourWolfpack game account, and reviewers must request one by email.
Installation
In SourceWeft
- Open BuildYourWolfpack in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.buildyourwolfpack%2Fwolfpack/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"buildyourwolfpack": {
"type": "http",
"url": "https://buildyourwolfpack-1.onrender.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 13, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.