API and personal keys

Most people never need this page. It is for builders who want to connect Mukala to their own tools.

The Mukala endpoint

Mukala speaks the standard protocol AI apps use to talk to tools. One address for everything:

https://mcp.mukala.ai/mcp

Claude and ChatGPT connect here with a normal Mukala sign in. You do not need a key for that.

Personal keys

For your own scripts or apps that cannot do a sign in, use a personal key.

• A key looks like mk_xxxxxxxx.xxxxxxxxxxxxxxxx (this is a placeholder, not a real key).
• Send it as a header: Authorization: Bearer YOUR_MUKALA_KEY
• One key belongs to one shop. Your role on that shop decides what the key can do.
• Keys expire, and you can revoke one at any time. Mukala only keeps the last four characters, so copy it when it is shown.

Example: list your products

curl https://mcp.mukala.ai/mcp \
  -H "Authorization: Bearer YOUR_MUKALA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_products","arguments":{}}}'

Example: invite a teammate

Admins can add someone with the invite_member action. It takes two steps: the first call shows what will happen, and the second call with your yes sends the invite.

Good to know

• Reads are open to anyone on the shop. Changes need the right role and your yes.
• There are daily limits per shop. See Roles and safety.
• Need something that is not here? Email todd@mukala.ai.