Connect your agent
The CLI sets everything up. To do it by hand, point any MCP client at your organization's MCP address.
Every organization has its own MCP server at https://{org}-mcp.sddvault.com/mcp, for example https://acme-mcp.sddvault.com/mcp. It uses the Streamable HTTP transport and is named sdd-vault in your agent.
The agent can sign in in two ways:
- Browser sign-in (recommended): the agent opens your organization's sign-in the first time it connects. No secret is stored in any file, so the configuration can be committed.
- Agent token: for CI, remote machines and agents that cannot open a browser. See Agent tokens.
Claude Code
Then run claude and ask "show the project status".
Cursor, VS Code, Windsurf and other clients
sddvault init writes the file each agent reads: .mcp.json (Claude Code and other clients), .cursor/mcp.json, .vscode/mcp.json and, for Windsurf, ~/.codeium/windsurf/mcp_config.json. Choose the agents with --agent (claude, cursor, vscode, windsurf or generic), repeated for several.
Written by hand, .mcp.json looks like this:
Cursor uses the same content without the type field, in .cursor/mcp.json. VS Code uses a servers key instead of mcpServers, in .vscode/mcp.json.
With a token
With a token, the agent sends Authorization: Bearer followed by the token. Keep the token in the SDD_VAULT_TOKEN environment variable so no secret is ever committed.
sddvault tokens create. A token is shown once; copy it right away.