Bespoke,
for agents.
A small Model Context Protocol server, so Claude and other agents can ask Bespoke's adviser, search its guides and hand people straight into the studio.
Tools
| Tool | What it does |
|---|---|
ask_bespoke | Asks the same guarded adviser as the button in the corner: how Bespoke works, or what to choose, with an optional design for context. |
search_guides | BM25 search over Bespoke's guides, run locally. Returns the best passages with titles. |
studio_link | A link that opens the studio on a fresh design, the board, the sheet or shopping. |
Connect it
The server lives in mcp/ and runs over stdio with Node 20 or later.
git clone https://github.com/riteshroshann/onestyle
cd onestyle/mcp && npm install
Claude Code
claude mcp add bespoke -- node /path/to/onestyle/mcp/server.js
Claude Desktop and other clients
{
"mcpServers": {
"bespoke": { "command": "node", "args": ["/path/to/onestyle/mcp/server.js"] }
}
}
Set BESPOKE_URL to point ask_bespoke and links at another deployment, such as a local one.
Try it
> Which colours suit a maroon silk kurta for a winter wedding? Use Bespoke.
ask_bespoke({ question: "Which colour palette suits it?", design: "for men, maroon, silk, kurta, for wedding" })
studio_link({ view: "new" })
The adviser keeps the product's guardrails: off-topic questions and attempts to change its rules are refused, and it never invents links.