MCP server
Connect your assistant to Kalepio through the Model Context Protocol. It reads and runs the studio you authorise it for, with your own rights and never more.
Server address
https://kalepio.com/mcpAdd this in your assistant's MCP settings. It will send you here to sign in and choose the studio, and no key has to be copied anywhere.
How the connection is authorised
- One connection works in one studio, chosen by you on the consent screen. To work in a second, connect a second time.
- An assistant never does more than you. Each call is allowed only where the connection's scope and your own rights in that studio agree, so a refusal means the studio has not granted it to you.
- Every connection is listed in your account settings and can be cut off in one click.
Tools (41)
What follows is what your assistant is sent when it asks for the list, word for word: this page is built by reading the server itself, so it cannot describe a tool that is not there.
Tool names and descriptions stay in English: that is the language the server speaks to assistants in, and translating them here would make two texts that could drift apart.
What it deliberately cannot do
Change a service, the public catalogue, the studio's members or its subscription. Those go through the studio's own screens, and it is a decision rather than a gap: what a studio sells and who works there is settled by looking at it. Files are attached by giving a public https address to fetch from: MCP has no way to hand a tool a file, so anything that is not already on the web goes through the studio's screen.