Skip to content
Siglata Docs
English
PortuguêsEnglish
Esc
↑↓navigate↵open⌘Jpreview
On this page

Connect Claude Desktop

Add Siglata as a remote connector in Claude Desktop, then sign in and choose your organization.

Connect Claude Desktop to Siglata through a custom remote connector. Add the server URL in Customize > Connectors, then sign in to Siglata. This path is installable / spec-compatible for v1 (Cursor and Codex are the proven clients).

Before You Start

  • A Siglata account. Sign in once at the Siglata Console. See Sign in.
  • Claude Desktop, installed and up to date.

If you use Claude Team or Enterprise, ask an Owner to add Siglata under Organization settings > Connectors first. The Owner selects Add > Custom > Web and uses the server URL below. Each member then connects their own Siglata account.

Add the connector

  1. Open Customize > Connectors in Claude Desktop.

  2. If Siglata is already listed, continue to Connect your account.

  3. For an individual account, select + > Add custom connector.

  4. Name the connector siglata and enter this URL:

    https://www.siglata.com/v1/mcp

  5. Select Add.

Connect your account

  1. Find siglata in Customize > Connectors and select Connect.
  2. Sign in to Siglata with your email magic link if needed.
  3. Choose the Siglata organization this connection may reach.
  4. Approve the requested permissions.
  5. In your conversation, open + > Connectors and enable siglata.

The remote connector is configured through your Claude account. See Anthropic’s remote connector instructions for account and workspace requirements.

You’re Done When

  • Customize > Connectors shows siglata as connected.
  • The server lists exactly two tools, execute and search.
  • You ask Claude to list the files in your Siglata organization, and it answers with your files.

Troubleshooting

  • Siglata is missing from your Team or Enterprise workspace. Ask an Owner to add the remote connector, then connect your account.
  • The sign-in window closed before it finished. Select Connect again from Customize > Connectors.
  • The agent reads the wrong organization. Disconnect Siglata and reconnect it. Choose the correct organization during authorization.
  • The tools are missing from the conversation. Open + > Connectors and enable siglata.
  • Calls fail with 401. Your grant ended, because the session was revoked or your membership changed. Reconnect Siglata to authorize a fresh grant.

What the Agent Can Do

Claude can list files and folders, upload new ones, download and read them, rename them, move them, send them to the trash, and restore them within 30 days. It can also read your organization’s profile, list members, invite people, and change roles. It never reaches past the organization you picked, and never past the permissions you approved.

The full operation list, with the permission each one needs, is in MCP.

For Agents

  • Add the remote connector in Customize > Connectors, then select Connect for siglata.
  • Server URL: https://www.siglata.com/v1/mcp. Transport is Streamable HTTP and authorization is OAuth 2.0.
  • tools/list returns exactly two tools, execute and search. There is no context tool.
  • Management operations are CallScript functions called inside an execute script, not MCP tools. Call search to list the operations this grant may call.
  • Call principal_get inside an execute script to read the bound organizationId, plus userId, role, and scopes.
  • Other clients: Connect.

Was this page helpful?