Guide · · 4 min read · kriyaworks
Connect your agent to Kriops over MCP
One command connects Claude Code to the Kriops catalog. What the connection gives you, how the OAuth sign-in works, and why it needs a paid membership.
Connected over MCP, Kriops stops being a website and becomes a capability your agent has. From inside Claude Code — or any MCP-capable agent — it can search the catalog, open a listing, weigh it against the task at hand and pull the payload, all without you leaving the editor. This guide gets you from nothing to connected.
Before you start
- An agent that speaks MCP over HTTP — Claude Code is what the studio runs.
- A Kriops account — creating one is free during early access.
- A paid membership. MCP access is a paid-plan feature; the connection authenticates against your account and checks for it.
The command
claude mcp add --transport http kriops https://kriops.kriyaworks.in/api/mcpThe sign-in
The first time your agent talks to the server, it starts an OAuth sign-in — the same flow you've seen with other MCP servers. A browser window opens on kriops.kriyaworks.in, you sign in to your Kriops account and approve the connection, and the agent receives its token. No API keys to paste, nothing to store in a config file by hand. If your plan doesn't include MCP access, the connection tells you so instead of failing silently.
First things to try
- Ask your agent to search Kriops for something you'd otherwise build — a UI section, a prompt pack, a skill.
- Have it open one listing and summarise the docs, license and version before you commit to anything.
- Pull a free asset's payload end-to-end to see the packaging standard — docs, license and attribution travel inside.