Connect Claude to zerosoft.
And use it from your terminal.
One connector reaches all 20 apps. You sign in through the browser with your normal login, with no keys to paste, and Claude acts as you, with your role and permissions.
claude.ai and Claude Desktop
In claude.ai, open Settings, then Connectors, and choose Add custom connector. Name it zerosoft.
Paste this URL and add it:
https://zerosoft.ai/api/mcpChoose Connect. Sign in to zerosoft if you are not signed in, pick the workspace and the access, and approve.
Claude Desktop and the Claude mobile apps use the connectors of your Claude account: add it once in claude.ai and it shows up there too. In a chat, turn zerosoft on from the tools menu.
On Claude Team and Enterprise plans, an owner adds the connector for the organization first. Then each person connects their own zerosoft account.
Claude Code
Add the server:
claude mcp add --transport http \
zerosoft https://zerosoft.ai/api/mcpRun /mcp inside Claude Code, pick zerosoft and sign in. Your browser opens the permissions screen.
ChatGPT
With developer mode turned on in ChatGPT, create a connector with the URL above and OAuth as the authentication. ChatGPT opens the same permissions screen.
Cursor and other editors
Add zerosoft to .cursor/mcp.json (or the MCP settings of your editor) with the URL below. Cursor opens the browser to sign in the first time. If your editor does not support OAuth for remote servers, use the API key version.
{
"mcpServers": {
"zerosoft": { "url": "https://zerosoft.ai/api/mcp" }
}
}Any MCP client or agent harness
The server speaks Streamable HTTP (MCP 2025-11-25, also 2025-06-18 and 2025-03-26) at a single URL, answers in JSON and keeps no session. Clients that do OAuth find everything from the 401: the WWW-Authenticate header points to the protected resource metadata, which points to the authorization server with dynamic client registration and PKCE.
Harnesses that cannot open a browser use an API key as a Bearer token. Create it in Settings, API and webhooks, turn on MCP access and pick its scopes: the key acts as you, limited by those scopes. Each key allows 300 reads and 60 writes per minute.
Most used tools have their own name, so a model does not need to search for them. Everything else is reached with search_operations, get_operation_schema and invoke_operation.
# Claude Code with an API key
claude mcp add --transport http zerosoft \
https://zerosoft.ai/api/mcp \
--header "Authorization: Bearer $ZEROSOFT_API_KEY"
# Any client: JSON config with a header
{
"mcpServers": {
"zerosoft": {
"type": "http",
"url": "https://zerosoft.ai/api/mcp",
"headers": { "Authorization": "Bearer zs_..." }
}
}
}
# Raw HTTP
curl -s https://zerosoft.ai/api/mcp \
-H "Authorization: Bearer $ZEROSOFT_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Tools with their own name
whoami, list_workspaces, list_apps, search_operations, get_operation_schema, invoke_operation, search_workspace, list_notifications, list_crm_contacts, create_crm_contact, list_group_chats, read_group_messages, send_group_message, update_group_chat, list_track_issues, get_track_issue, create_track_issue, update_track_issue, comment_on_track_issue, search_docs, get_doc_page, create_doc_page, update_doc_page, list_boards, get_board
OAuth
https://zerosoft.ai/.well-known/oauth-protected-resource/api/mcp
https://zerosoft.ai/.well-known/oauth-authorization-serverThe zerosoft CLI
Same reach, for the terminal and for scripts. It prints tables in a terminal and JSON when piped or with --json.
The CLI is not on npm yet. From a copy of the repository, run it with:
cd cli && npm link
# or: node cli/bin/zerosoft.mjs --helpExamples
zerosoft login
zerosoft whoami
zerosoft apps
zerosoft ops search "deal move"
zerosoft ops show crm.deals.update
zerosoft crm contacts list
zerosoft track issues create \
--projectId p1 \
--title "Fix the invoice"
zerosoft call crm.deals.update --json \
'{"path":{"id":"d1"},
"body":{"priority":"high"}}'
zerosoft setup claudeOn a machine with no browser, zerosoft login --device shows a code that you approve from any other device. The token goes to the OS keychain when there is one, and otherwise to a file only you can read. For CI, set ZEROSOFT_API_KEY.
How Claude finds things
There are about 1,800 operations, so they are not listed one by one. Claude uses a few tools: list_apps, search_operations, get_operation_schema and invoke_operation, plus whoami and shortcuts for common actions.
Each operation runs the same code as the app. Most have an exact input schema derived from the code; some are marked partial or loose, and then Claude learns from the error message.
What it can do
Disconnecting stops the connection. What it created stays, and flows, CRM workflows and robots it turned on keep running until you turn them off. Turning one on asks for an explicit confirmation.
It can do what you can do, nothing more. If your role, your app access or a private channel stops you in the app, it stops Claude too.
In the permissions screen you choose read and write, or read only, and the workspace. Destructive operations ask for an explicit confirmation from the client.
See and disconnect your connected apps in Settings, API and webhooks. Changes made through a connection are recorded with the person, the app and the operation.
What comes back from zerosoft may include text written by other people, such as customer messages or emails. It reaches Claude marked as data, not as instructions. Still, review what Claude proposes before it sends or deletes something.
Passing to another workspace takes reconnecting: a connection stays in the workspace you chose when you approved it.
Clients must use an https or local redirect address. Custom URL schemes are not supported.
What stays out
- Signing in, API keys and OAuth clients. Workspace ownership, account deletion and billing. Those stay in Settings.
- Public visitor pages, inbound webhooks, cron jobs and Pulse ingest. No person is behind them.
- Flows that need your browser, such as connecting Gmail or a social network, and realtime streams.
Done in the web app
These create something that keeps working after you disconnect, or store the keys of another service. Claude and the CLI tell you where to do them.
- Webhooks, incoming hooks and slash commands; Track agent apps and the GitHub connection.
- Payment keys and integration keys: Shop, Cal, Books, CRM apps, Flow credentials and agent secrets.
- Shareable links for docs, notes, boards, designs and recordings.
- Inviting people to the workspace; Lines numbers and their provider keys; imports that hold another service's token.
- Webhook addresses on forms and webhook steps in Cal.
- Giving someone the admin or owner role.
With an API key
The endpoint also accepts a personal API key as a Bearer token, for clients without OAuth. Create the key with MCP access in Settings, API and webhooks: other keys keep working with the REST API only. It is limited by the scopes of the key.