Connect an AI assistant (MCP)

MCP is how AI assistants plug into other apps. Connect Wujud and you can ask Claude things like “turn this paragraph into a voiceover” or “how many AI credits do we have left?”, and it does it in your workspace.

The assistant works through an API key, so it can do exactly what that key can do and nothing else. It acts in one workspace, the one the key belongs to.

Connect it

1. Create an API key under Developer then API Keys. Tick only the scopes you want the assistant to have.

2. Add Wujud to your assistant. In Claude Code:

   claude mcp add --transport http wujud https://mcp.wujud.app/mcp \
     --header "X-API-Key: wujud_sk_your_key_here"

   Using Claude Desktop or claude.ai instead? See below.

   Other clients that take a remote MCP server want the same two things: the URL https://mcp.wujud.app/mcp and the header X-API-Key: wujud_sk_your_key_here.

3. Ask it something. “Which Wujud workspace are you connected to?” is a good first check.

Claude Desktop and claude.ai

Add Wujud once as a custom connector and it shows up in both.

1. In Claude, open Settings then Connectors and press Add custom connector.

2. Name it Wujud and paste https://mcp.wujud.app/mcp as the URL.

3. Under Authentication, pick No sign-in. Wujud uses an API key, not a sign-in.

4. Under Request headers, add a custom header named X-API-Key with your key as the value, just wujud_sk_… with nothing in front.

5. Press Add. Leave the transport on Streamable HTTP.

Working across two workspaces? Make a key in each and add Wujud twice under different names.

What it can do

The assistant only sees the tools your key can use, and only for features Wujud has switched on.

Scope	What the assistant can do
Always	Tell you which workspace it’s in and what the key can reach
Usage	Check plan usage, AI credits and AI spend history
Media	List and look up files in the media library
AI	Every AI tool that’s switched on, each as its own tool, with a cost estimate before it runs, and checking on the job

Which scopes a key can hold depends on your plan, see the table on the API keys page. AI and Usage are on every plan, Free included.

It spends what you'd spend

AI tools run from the assistant use the workspace’s AI credits, the same as in the dashboard. Assistants usually ask first, but a narrowly scoped key is the surest guard.

Limits

Every tool call is an API request, so it counts toward your plan’s daily API requests (100 a day on Free). The assistant also checks what your key can do when it loads its tools, which costs one request now and then.

When something isn’t allowed, the assistant gets Wujud’s reason word for word, like “the AI scope is not enabled on your plan”, and can tell you what to change.

Turning it off

Revoke or edit the key under Developer then API Keys. The assistant loses access straight away.