Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Use Chetty as an MCP server
Skills, MCP and API

Use Chetty as an MCP server

Let an external MCP client, such as a desktop AI tool, work with Chetty through one generic request tool. This is the opposite direction from connecting external MCP servers.

Before you start

You need two things:

  • A personal API token; Create a token shows how.
  • The public address of this Chetty instance.

Every call runs with that token's account and permissions, so treat the token like a password and give it an expiry you can live with.

Add Chetty to your client

  1. In the MCP client, add a remote server and choose its streamable HTTP transport.
  2. Enter https://<your-elowen-address>/mcp as the server address.
  3. Send the token as a bearer credential in the Authorization request header.
  4. Save, then check that the server connects and lists a single tool, elowen_request.

The address is stateless: each request stands alone and no session is kept between calls.

What the tool does

elowen_request calls any Chetty HTTP API operation. It takes a method, a path and an optional body, and returns what the instance answers. The API reference lists every operation your account can call, with its inputs and the matching ElowenApi call, which takes the same arguments.

Account rules, Project access, plugin grants and tool policy apply exactly as they do in the Web UI, so the client can never do more than the token's account may do.

Warning: A token is not limited to one client. If it leaks, revoke it and new requests are refused immediately.

See Agent API for the same access over plain HTTP, and Create and manage a personal API token for limits and revocation.