Theme
MCP server
Zefi runs a remote MCP server, so an AI assistant can read your workspace and act in it while you are talking to it — rather than you copying answers between a chat window and the platform.
Unlike the REST API on the rest of this site, there is no key to create: you sign in as yourself, and the connection carries your own permissions.
text
https://mcp.zefi.ai/mcpThat URL is the whole configuration. Everything else — discovery, registration, sign-in — the client and the server negotiate between themselves.
Connect your client has the exact steps for Claude, ChatGPT, Cursor, VS Code, Codex, Antigravity and the rest.
One connection, one workspace
You pick a workspace when you connect, and the connection is fixed to it. No prompt, tool argument or file path can move it somewhere else, which is what stops an assistant wandering into a workspace you did not mean to open.
To work in a second workspace, connect a second time and choose it — most clients let you add the same server twice under different names.
Which workspaces are offered
The same ones the platform shows you, decided the same way. A workspace that enforces SSO only appears if you signed in through that workspace's identity provider — see Troubleshooting.
What you need
- A Zefi account that belongs to at least one workspace.
- A client that supports remote MCP servers over HTTP. Most current ones do.
- Nothing installed, and no key to create. You will not be asked for a secret at any point — if a client asks you to paste one, it is not talking to us.
Signing in
The first time a client connects it opens your browser, you sign in to Zefi as usual, and you approve the connection and the workspace. After that the client refreshes its own access; you will not be asked again unless you disconnect or lose access.
That approval screen names the client and shows the address your approval would actually be sent to, so a client claiming to be something it is not is visible before you approve it. A client that has not proved who it is carries a warning rather than its own branding.
What it can do
Your client lists the tools it can use once connected, and the set grows as we add to it — new tools appear on their own, with no reconnection and no version to pin.
Where to go next
| Connect your client | Step-by-step for every major client |
| Troubleshooting | What the errors mean, and what to do |
| Authentication | API keys, for the REST API rather than this |
