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 the US region. Other regions aren't served yet.
- 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.
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.
Two fields, nothing else
Name it Simetrik, and point it at:
https://mcp.us.simetrik.com/mcpIf 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.
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.
Sign in
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 register themselves: the server supports both client ID metadata documents and dynamic client registration, so whichever mechanism your client uses, there's nothing to set up by hand.
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.
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"
}
}
}