Connect an AI Agent (Hosted MCP)

Give any MCP-capable AI agent one URL, and it can manage mindzieStudio for you.

Every mindzieStudio server hosts an MCP (Model Context Protocol) server. Nothing needs to be installed: your agent connects to a URL with a mindzieStudio API key, and can then create projects, add users and load data, all by being asked in plain language.

The Quickest Way: Let the Agent Set Itself Up

Give your agent this one sentence:

The page in that sentence is written for the agent. It asks you which server you use, tells you where to create your API key, and walks you through adding the server to your agent. The key never goes into the conversation: you paste it into your agent's connector settings yourself.

What You Need

1. A tenant API key. This is the normal key, and the one to use. It opens your own tenant: its projects, users and datasets. In mindzieStudio, open the menu under your name, then Administration > Settings > API Keys, and create a key. You need the Administrator role in the tenant. The key is shown once, so copy it straight away.
2. An AI agent that supports MCP servers, such as Claude Cowork, Claude Code, Cursor, VS Code, or an agent built on the Grok or OpenAI APIs.

A Global API key opens every tenant on the server and can create new tenants. Only a server administrator can create one (menu under your name, Server Settings > Global API Keys), and only partners who set up tenants for their customers need one. See Setting Up a Customer in One Step.

The URL

Server	MCP URL
mindzieStudio (US)	https://www.mindziestudio.com/mcp
mindzieStudio Europe	https://europe.mindziestudio.com/mcp
Your own server	https://<your server>/mcp

There are two ways to pass the key:

Your agent can...	Enter
Send a header with a URL (Claude Cowork, Claude Code, Cursor, VS Code, agent APIs)	URL https://www.mindziestudio.com/mcp and header Authorization: Bearer <your API key>
Only take a URL	https://www.mindziestudio.com/mcp/k/<your API key>

Treat the second form like a password. The key is part of the URL, so anyone who sees the URL can use the key. Do not paste it into shared documents or chats. If it leaks, delete the key in mindzieStudio and create a new one.

Setting Up Your Agent

Claude Cowork / Claude desktop app

1. Open Settings > Connectors (on claude.ai: Customize > Connectors), choose Add, then Add custom connector. Connectors belong to your Claude account, so Cowork, the desktop app and claude.ai all get it.
2. Name it mindzie, and as the URL paste https://www.mindziestudio.com/mcp.
3. Under Authentication, choose No sign-in. Claude first suggests "Sign in now"; mindzieStudio uses an API key instead, and the authorization header can only be added once No sign-in is chosen.
4. Under Request headers, add the header authorization with the value Bearer <your API key> (the word Bearer, a space, then the key).
5. Save. Claude lists the mindzie tools. Start a new conversation and ask: "Using mindzie, who am I connected as?" Claude asks permission before each tool call.

If your Claude version shows no header option, use https://www.mindziestudio.com/mcp/k/<your API key> as the URL instead.

Claude Code

claude mcp add --transport http mindzie https://www.mindziestudio.com/mcp --header "Authorization: Bearer <your API key>"

Cursor / VS Code

Add to your MCP configuration (.cursor/mcp.json or .vscode/mcp.json):

{
  "mcpServers": {
    "mindzie": {
      "url": "https://www.mindziestudio.com/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

Grok, OpenAI and other agent APIs

Agent APIs that support remote MCP servers take a server URL and an authorization value. Use https://www.mindziestudio.com/mcp as the URL and Bearer <your API key> as the authorization. If the API takes only a URL, use the /mcp/k/<your API key> form.

Check the connection

Ask your agent to run mindzie_whoami. It answers with the server it reached and whether the key is global (canManageTenants: true) or limited to one tenant (keyTenantId: the tenant it opens).

Setting Up a Customer in One Step

This needs a Global API key, and is for partners who create tenants for their customers. With a tenant key, your agent works inside your own tenant instead.

The mindzie_provision_tenant tool sets a customer up completely in one call:

• creates the tenant,
• switches its modules on or off (Process Mining, Data Designer, BPM Studio, AI Process Intelligence),
• gives the admin user access (an existing account is reused; a new one is created),
• creates the projects, with the admin as owner, so the admin sees them at once.

Example prompt:

Using mindzie, provision a tenant named acme-corp with display name "Acme Corporation", 5 users and 2 analysts. Turn on Process Mining and Data Designer, and turn off BPM Studio and AI Process Intelligence. The admin is jane@acme.com (Jane Smith). Create the projects "Purchase to Pay" and "Order to Cash".

No email is sent. A new admin account is created without a password; the admin signs in by choosing Forgot password on the sign-in page, or you tell them their first password if you set one.

Many customers at once

Give the agent the list (for example a spreadsheet of company names, admin emails and modules) and ask it to provision each one and report the result per customer. If a run stops part way, ask it to run again with resumeExisting for the customers that already exist: steps that were done are reported as existing and nothing is duplicated.

Loading data

Use mindzie_upload_dataset_from_url with an https link to a CSV file of up to 1 GB, for example a cloud storage link with a read token. The mindzieStudio server downloads the file itself, so large files never pass through the chat. The link must be publicly reachable; links to private or internal network addresses are refused.

For a few thousand rows you can also paste the CSV text with mindzie_upload_dataset_csv_text.

Available Tools

Tool	What it does	Key needed
mindzie_whoami	Server and key information	Any
mindzie_provision_tenant	Tenant, modules, admin and projects in one call	Global
mindzie_list_tenants, mindzie_get_tenant	Read tenants	Global
mindzie_create_tenant, mindzie_update_tenant	Create or change a tenant	Global
mindzie_delete_tenant	Permanently delete a tenant (id, name and display name must all match)	Global
mindzie_get_tenant_settings, mindzie_set_tenant_modules	Read settings; switch modules on or off	Global
mindzie_list_tenant_users, mindzie_add_user_to_tenant, mindzie_find_user_by_email	Tenant users	Global or tenant
mindzie_list_projects, mindzie_get_project, mindzie_create_project, mindzie_update_project, mindzie_delete_project	Projects	Global or tenant
mindzie_list_project_members, mindzie_add_project_member	Who can see a project	Global or tenant
mindzie_list_datasets, mindzie_upload_dataset_csv_text, mindzie_upload_dataset_from_url	Datasets	Global or tenant

Every tool follows exactly the same rules as the REST API: the same permissions, validation and error messages.

Good to Know

• A bare tenant has the server's default modules, which may not be what a customer expects. Use mindzie_provision_tenant, or set the modules explicitly with mindzie_set_tenant_modules.
• A project is visible only to its members. A project made with mindzie_create_project has no members until you add them with mindzie_add_project_member. mindzie_provision_tenant does this for you.
• Deleting is permanent. A good agent confirms with you first; the delete tools require the exact names.
• Every tool call is logged on the server with the name of the API key that made it.

Troubleshooting

What you see	Why	What to do
HTTP 401 / "unauthorized" when connecting	The key is wrong, deleted, or for another server (each region has its own keys)	Create a key on the server you are connecting to
"requires a Global API key"	A tenant key was used for a tool that works across tenants (listing, creating, changing or deleting tenants, tenant settings or modules)	Those tools are for server administrators and partners who set up tenants. Work inside your own tenant with the project, user and dataset tools. If you do create tenants for other companies, see Setting Up a Customer in One Step
"does not have access to tenant"	The tenant id is not the key's tenant	Use keyTenantId from mindzie_whoami
The admin signs in and sees no projects	They are not a member of the projects	mindzie_add_project_member, or provision with mindzie_provision_tenant
"already exists" from provision	The tenant name is taken	If it is the same customer, run again with resumeExisting; otherwise choose a different name
"non-public address" when loading data	The link points to a private or internal network	Use a publicly reachable https link