Connect

Who adds the server, how each person turns it on, and the one permission setting worth changing.

Before you start

Three things must hold, or the workspace won't appear when you connect:

A Simetrik account — your everyday one. There's nothing new to create.
A production workspace in a region the server covers — see Pick your region.
CLI/agent access on that workspace, and the Use CLI permission on your role.

The last one is granted by an account or security administrator in a single step: send them Enable a role for CLI use — that page is the whole procedure.

It works in the browser and in the desktop app. You set it up once and it's in both.

Pick your region

Each Simetrik region runs its own server, and the address has to match the region your account lives in. Look at the address bar while you're signed into Simetrik:

If you sign in at…	your server address is
`app.simetrik.com`	`https://mcp.us.simetrik.com/mcp`
`app.ie.simetrik.com`	`https://mcp.ie.simetrik.com/mcp`
`app.mx.simetrik.com`	`https://mcp.mx.simetrik.com/mcp`
`app.br.simetrik.com`	`https://mcp.br.simetrik.com/mcp`
`app.in.simetrik.com`	`https://mcp.in.simetrik.com/mcp`

The United States app has no region in its address, but its server does (mcp.us). The examples below use the US address — swap in yours.

A wrong address never shows you another region's data: your sign-in is only valid in your own region, so the connection simply fails.

Who adds it

That depends on who owns the Claude account, and it changes what you do next:

Team or Enterprise — whoever administers Claude adds it once for the whole organization. Everyone else then turns it on from their own account without ever typing the address.
Individual account — you do both halves yourself. On the Free plan you get one custom connector; Pro and Max have no limit.

If your company administers Claude and you aren't an administrator, adding it yourself files a request for an administrator to approve with one click. It would technically also work on a personal Claude account — the access still comes from your own Simetrik login — but that puts your company's data in an account your company doesn't administer. Ask your security team first.

Add it once, for the organization

Skip this section if the Claude account is your own.

Organization → Connectors

From Claude's side menu.

+ Add → Custom

Two fields, nothing else

Name it Simetrik, and point it at your region's address, for example:

https://mcp.us.simetrik.com/mcp

If Advanced settings appears with OAuth fields, leave it closed.

It's now available to the whole team. Each person turns it on from their own account below — they never see the address.

Turn it on in your account

Your name → Settings

Bottom left.

Connectors, under Customize

Find Simetrik and press Connect

If an administrator added it for the organization, the address is already filled in.

Setting it up for yourself instead? Use Add custom connector, paste the URL above, and leave everything under Advanced empty.

A browser tab opens. Sign in with your Simetrik account (Google / SSO).

There's no API key to create, copy or rotate — your client never handles a Simetrik credential.

Clients that support it register themselves: the server accepts both client ID metadata documents and dynamic client registration, so with either mechanism there's nothing to set up by hand. If your client asks for a client ID and secret instead, see Clients that need a client ID and secret in Security and network.

Pick your workspaces — if you have more than one

If your account has two or more workspaces with CLI/agent access, a picker appears: select one or several, then Connect selected.

If you have exactly one, there is nothing to choose and you won't see this screen — the connector goes straight through and that workspace becomes your default. That is the normal path, not a failure.

Put the read-only actions on Always allow

Worth doing, and it takes one click. Under the connector's Tool permissions, set Read-only tools to Always allow.

Sixteen of the nineteen actions only read — they can't change anything (why that's structural, not a setting). Without this, Claude asks your permission on every single call, which turns one question into a dozen prompts.

Ask something

The quickest check that it worked: ask "which Simetrik workspaces do I have access to?" If it names them, you're connected.

First conversation

You're connected to my Simetrik workspace. Give me an overview: how many resources I have, of what types, and which reconciliations ran most recently. Don't change anything — just show me what's there.

Paste this once connected to confirm the MCP server can reach your workspace.

Other MCP clients

Nothing above is Claude-specific except the menus. Any client that speaks remote MCP can use the same URL.

Settings → MCP → Add new MCP server, or add it to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "simetrik": {
      "url": "https://mcp.us.simetrik.com/mcp"
    }
  }
}

Add it to .vscode/mcp.json:

{
  "servers": {
    "simetrik": {
      "type": "http",
      "url": "https://mcp.us.simetrik.com/mcp"
    }
  }
}

Add it from the terminal:

gemini mcp add --transport http -s user simetrik https://mcp.us.simetrik.com/mcp

Then open gemini and run /mcp auth simetrik to sign in. Run /mcp to confirm it's connected and lists its tools. No token or OAuth settings are needed — Gemini CLI discovers the sign-in and registers itself.

Requires n8n 1.119 or later.

In your workflow, add an AI Agent node with the MCP Client Tool.
Server transport: HTTP Streamable. Endpoint: your region's address.
Authentication: an MCP OAuth2 credential with dynamic client registration. Connect it, sign in with your Simetrik account and pick your workspaces.

Using n8n's generic OAuth2 credential instead (it asks for a client ID and secret)? See Clients that need a client ID and secret in Security and network.

Add the server as an MCP tool and choose OAuth 2.0 with dynamic discovery: Copilot reads the server's metadata and registers itself with a client secret, which the server issues and enforces.

If your tenant registers MCP servers manually instead, follow Clients that need a client ID and secret in Security and network.

On this page