sxmcp lets you reach the systems you have connected to StudioX, and look after
them, from a terminal or a script. With it you can:
- see your connected systems (your MCP servers) and every tool each one has;
- read what a tool needs and run it, with arguments typed inline or from a file;
- add a server, change it, turn it on or off, re-read an external server's tools, remove it;
- set or rotate the credential a server uses to reach the system behind it — it is never shown back;
- issue and revoke the credentials other callers use for a server's endpoint, and decide whether one is needed;
- share a server with a colleague, or stop sharing it;
- browse the prebuilt catalogue and install from it;
- read the audit log of what happened on your servers.
It does what the Integrations screens do, with the same rules about who may see, run and change what. One file per platform, nothing else to install.
Install
Download the file for your computer from www.studiox-ai.com/downloads/mcp-cli:
| Your computer | File |
|---|---|
| Mac with Apple silicon | sxmcp-darwin-arm64 |
| Mac with Intel | sxmcp-darwin-amd64 |
| Windows | sxmcp-windows-amd64.exe (or the sxmcp-windows.zip bundle) |
| Linux | sxmcp-linux-amd64 or sxmcp-linux-arm64 |
On a Mac or Linux, make it runnable and put it on your path:
chmod +x sxmcp-darwin-arm64
sudo mv sxmcp-darwin-arm64 /usr/local/bin/sxmcp
sxmcp version
On a Mac, if it is blocked the first time, allow it under System Settings →
Privacy & Security. On Windows, rename it to sxmcp.exe and put it in a folder on
your PATH.
You can check a download against SHA256SUMS:
shasum -a 256 -c SHA256SUMS --ignore-missing
Sign in
You need a token. In Integrations, open Settings → API access, give the token a label, choose an expiry and what it may do, and select Make token. Copy it — it is shown once.
Then save it for your installation:
sxmcp configure --base https://www.studiox-ai.com/mcp
sxmcp asks for the token and checks it before saving anything:
Saved profile "default": www.studiox-ai.com as dana@your-company.com (personal token, every scope).
In a script, pipe the token in instead of typing it:
printf '%s\n' "$MCP_TOKEN" | sxmcp configure --base https://integrations.your-company.com/mcp
The token is stored in ~/.studiox-mcp.json, readable only by you.
Which token to use:
| Token | Use it when |
|---|---|
A personal token (mcp_pat_…) |
You are working, or running your own scripts. It acts as you and runs on your StudioX sign-in, so open Integrations in your browser now and then. |
A service token (mcp_svc_…) |
Something runs on its own — CI, a scheduler, another system. A business administrator makes it in Settings → Service tokens for a StudioX user created for that system. It needs nobody signed in. |
A StudioX API key (sx_live_…) |
You already have one. It acts as you with everything your role allows. |
Check who you are:
sxmcp whoami
dana@your-company.com on www.studiox-ai.com
signed in with personal token, may run, manage
role business-admin
businesses acme
servers 12 you can see
More than one installation
Give each installation a profile name:
sxmcp configure -p prod --base https://www.studiox-ai.com/mcp
sxmcp configure -p onprem --base https://integrations.your-company.com/mcp
sxmcp profiles
sxmcp use onprem
sxmcp -p prod servers
--base URL picks the profile you made for that address; a token is never sent to
an address it was not made for. MCP_BASE and MCP_TOKEN in the environment take
the place of the profile — handy in CI.
Your servers
sxmcp servers
sxmcp servers --search jira
sxmcp server get jira
ID ADDRESS NAME KIND STATE TOOLS YOURS
6c1d0e3a-… acme/jira Jira external on 40 owned
91f2c4b7-… acme/weather Weather internal on 3 business
Wherever a command takes SERVER, you can give its id, its slug (jira), its
address (acme/jira) or its name. If a name matches more than one, sxmcp lists
them so you can pick by id.
Add, change, turn off and on, remove:
sxmcp server add --name "Field Service" --external https://mcp.example.com/mcp
sxmcp server rediscover field-service # read its tools from the server
sxmcp server set field-service --description "Work orders and technician schedules"
sxmcp server disable field-service
sxmcp server enable field-service
sxmcp server rm field-service # asks first; --yes to skip the question
For everything a server can be created with, give the JSON yourself:
sxmcp server add --from @server.json.
Running tools
sxmcp tools jira
sxmcp tool get jira search_issues # what it needs
sxmcp tool run jira search_issues jql="project = OPS AND status = Open"
Give arguments as name=value (a value that is valid JSON — 3, true,
{"a":1} — is sent as that, anything else as text), or all at once:
sxmcp tool run weather forecast --args '{"city":"Oslo","days":3}'
sxmcp tool run weather forecast --args @args.json
cat args.json | sxmcp tool run weather forecast --args -
An answer made of text is printed as text; anything else as JSON. --raw always
prints the whole result, --json the API's full answer.
A tool that runs and fails exits with status 1 and shows what the system behind it said:
sxmcp: upstream said 404 [HTTP 502 upstream_error]
returned: {"message":"city not found"}
hint: the system behind the server refused or failed — `returned` above is what it said
Credentials a server uses
sxmcp credentials jira
sign-in bearer — fields: token
SECRET SCHEME SET
API_KEY 2026-10-18 12:02
Values are never shown, only what is set. To rotate:
sxmcp auth set jira --mode bearer --config '{"token":"the-new-token"}'
sxmcp secret set weather API_KEY # asks for the value, or pipe it in
printf '%s\n' "$NEW_KEY" | sxmcp secret set weather API_KEY
A blank field keeps what is stored. Remove with sxmcp auth rm SERVER and
sxmcp secret rm SERVER KEY.
Who may use a server
See it all at once:
sxmcp access weather
A server's endpoint is open unless you require a credential. Issue one, then switch it on:
sxmcp client add weather ops-portal # prints the secret, once
sxmcp access set weather bearer
Callers then send Authorization: Bearer <secret>. Other ways:
sxmcp access set weather api_key --header X-Subscription-Key, or basic with the
credential's name as the username. Revoke with sxmcp client rm weather CLIENT_ID;
open it again with sxmcp access set weather none.
Share a server with a colleague, read-only or as admin:
sxmcp share add weather dana@your-company.com
sxmcp share add weather lee@your-company.com --admin
sxmcp shares weather
sxmcp share rm weather dana@your-company.com
The catalogue
sxmcp templates servicenow
sxmcp template get servicenow
sxmcp template install servicenow
template get lists what the API behind it needs from you; set those with
sxmcp secret set after installing. Installing one you already have tells you so,
and names tools the catalogue gained since; --reconcile adds them.
The audit log
sxmcp audit --server weather
sxmcp audit --status error --page-size 20
sxmcp audit --category api # everything done through the API
Scripts and CI
- Every command takes
--jsonand prints the API's answer as JSON. - Exit codes: 0 done, 1 refused or failed (the message and a hint are on stderr), 2 the command line was wrong.
- Commands that remove something ask first on a terminal; in a script, pass
--yes, or they stop with exit 2. - Use a service token, through the environment:
export MCP_BASE=https://integrations.your-company.com/mcp
export MCP_TOKEN=mcp_svc_…
sxmcp tool run inventory reorder sku=A-1042 qty=40 --json | jq .result
sxmcp openapi --out integrations-api.jsonsaves the API description (no token needed) for Postman, Swagger UI or a client generator.
When something goes wrong
| You see | What to do |
|---|---|
unauthorized |
The token is unknown, revoked or expired. Make a new one and run sxmcp configure. |
studiox_session_stale |
A personal token's StudioX sign-in has lapsed. Open Integrations in your browser once, then retry — or use a service token. |
scope_missing |
The token was not made for this. Make one with the scope named. |
forbidden |
Your access to this server does not allow it. Ask its owner to share it with you as Admin. |
not_found |
Check the name or id; sxmcp servers lists what you can see. |
conflict |
It is in a state that refuses this; the message says why. |
rate_limited |
Too many requests for this token; wait the seconds shown. |
upstream_error |
The system behind the server refused or failed; its answer is shown. |
could not reach |
Check the address with sxmcp profiles, and your network or VPN. |
Command reference
sxmcp configure [-p NAME] [--base URL] token from stdin
sxmcp profiles | use NAME | profile rm NAME
sxmcp whoami
sxmcp servers [--search S] [--sort recent|name|verified] [--limit N] [--offset N]
sxmcp server get|enable|disable|rediscover SERVER
sxmcp server add --name N [--description D] [--slug S] [--scope business|personal] [--owner BUSINESS] [--external URL]
sxmcp server add --from JSON|@file|-
sxmcp server set SERVER [--name N] [--description D] [--slug S] [--url URL] [--timeout-ms N|none] [--share-domain D]
sxmcp server rm SERVER [--yes]
sxmcp tools SERVER [--schema]
sxmcp tool get SERVER TOOL
sxmcp tool run SERVER TOOL [--args JSON|@file|-] [name=value …] [--raw]
sxmcp credentials SERVER
sxmcp auth set SERVER --mode MODE [--config JSON|@file|-]
sxmcp auth rm SERVER [--yes]
sxmcp secret set SERVER KEY [--value V]
sxmcp secret rm SERVER KEY [--yes]
sxmcp access SERVER
sxmcp access set SERVER none|bearer|api_key|basic [--header NAME] [--auto-mint on|off]
sxmcp clients SERVER
sxmcp client add SERVER NAME
sxmcp client rm SERVER CLIENT_ID [--yes]
sxmcp shares SERVER
sxmcp share add SERVER EMAIL [--admin]
sxmcp share rm SERVER SHARE_ID|EMAIL [--yes]
sxmcp templates [--search S] [--category C] [--featured] [--limit N] [--offset N]
sxmcp template get SLUG
sxmcp template install SLUG [--owner BUSINESS] [--reconcile]
sxmcp audit [--server SERVER] [--category C] [--action A] [--status success|error] [--search Q] [--page N] [--page-size N]
sxmcp openapi [--out FILE]
sxmcp version
Everywhere: --json, -p/--profile NAME, --base URL; MCP_BASE and MCP_TOKEN override the profile.