When we sketched the first version of Puras, we asked a simple question: who is actually going to type the commands that deploy a skill?
The honest answer was: not the developer. Increasingly, it's the agent sitting next to the developer in Claude Code or Cursor. So we built the developer experience for that agent first.
What that means in practice
- The MCP server (
purasbackend-mcp) is the primary surface. Every REST endpoint has a mirror as an MCP tool. - Docs ship inside the MCP package as markdown, surfaced via
list_docs,read_doc, andsearch_docstools — so the agent can ground its suggestions in real reference material without browsing the web. - The dashboard is for humans who want to see logs, balance, and outputs — not for daily development.
Why this is a wedge, not a gimmick
Anyone can wrap their existing API in an MCP server in an afternoon. The interesting work is in product surface area that only makes sense agentically: bundled deployments, auto-discovered skills (folder = skill, no manifest to keep in sync), and generic media tools the agent picks at runtime. We'll dig into each of those in upcoming posts.
