# What is Connector Central?

Connector Central sits between your team's AI and the apps you use to run your firm. Your team connects an AI client to one protected MCP endpoint, while Connector Central applies the selected workspace's current access rules.

## The workspace is the boundary

Each workspace has its own members, settings, connections, permissions, and activity history. Choosing a workspace during OAuth consent binds the issued token to that workspace. A token for one workspace cannot be reused for another.

## Access is evaluated live

The authenticated MCP `tools/list` response is the authority for what a person can use at that moment. Changing a person's membership or permissions, disabling access, or revoking the client changes later listings and calls without waiting for an existing token to expire.

## Credentials stay on the server

AI clients do not receive stored service credentials. Connector Central resolves an allowed connection on the server only when it dispatches an authorized tool call.

## The activity log stores metadata, not content

Connector Central records operational details such as the actor, operation, status, time, duration, and error category. It does not store prompts, tool arguments, tool results, or upstream request and response payloads.

## Next steps

- [Create your account](/docs/getting-started/creating-your-account)
- [Set up your first workspace](/docs/getting-started/setting-up-your-first-workspace)
- [Choose an AI client guide](/docs/connect-ai-clients/chatgpt)