tide_list
List all available content in the Tide agent pack by category
categoryrequired
io.github.tide-foundationPublished by GitHub account tide-foundationv1.9.34Updated Oct 29, 2026
MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
The publisher's own server: Raziel Calculators
Raziel is the Tide agent pack: an MCP server that gives coding assistants verified playbooks, skills and scenarios for implementing TideCloak auth, E2EE and…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.tide-foundation%2Fraziel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"raziel": {
"type": "http",
"url": "https://mcp.tide.org/mcp"
}
}
}Raziel is the Tide MCP — it gives AI coding agents the knowledge to implement TideCloak correctly.
This MCP server gives your AI assistant deep knowledge of Tide authentication, threshold cryptography, end-to-end encryption, IGA governance, and Forseti smart contracts — plus a security gap analysis of your existing system and self-host vs managed-hosting guidance. Instead of guessing, your AI follows verified playbooks.
Run this one command:
Done. Start a conversation and ask your agent to add Tide auth to your app.
Add a .mcp.json file to your project root:
Works with: Claude Code, Cursor, Windsurf, Cline, and any MCP-compatible tool.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Open Settings > MCP Servers > Add Server:
tide-packnpx-y @tideorg/mcpOr add to .cursor/mcp.json in your project root.
Add to ~/.codeium/windsurf/mcp_config.json:
Or for local: "command": "npx", "args": ["-y", "@tideorg/mcp"]
Add to your Zed settings (~/.config/zed/settings.json):
Note: Zed uses context_servers (not mcpServers) and doesn't yet support remote URL-based MCP servers — use the npx command.
Add to ~/.codex/config.json:
Note: Codex CLI currently supports stdio-based MCP servers only — use the npx command.
Lovable's build agent can use Raziel through a Custom MCP connector (available on all plans). In your Lovable project, open Connectors → Custom MCP (the card at the bottom) and add:
Razielhttps://mcp.tide.org/mcpNo authenticationThen tell the agent to use it — e.g. "Use the Raziel connector to pull the TideCloak playbook before writing any auth code."
Two things that trip people up:
Once connected, your AI assistant can:
After setup, try these prompts in your AI coding tool:
Do a security analysis of my app and show what Tide would change
Add Tide authentication to my Next.js app
I have an existing app with auth — help me migrate to Tide
Set up encrypted data sharing between users with Tide
Help me create a Forseti contract for multi-admin approval
We host the MCP server so you don't have to install anything. Just add the URL:
No Node.js required. No npx. Works with any MCP client that supports remote servers.
Want to run your own instance? Pull from Docker Hub:
Or build from source:
Then point your MCP client at http://localhost:3000/mcp.
Optional: set API_TOKEN environment variable to require Bearer token auth:
No TideCloak instance needed to start — the agent will guide you through setup.
The MCP server is read-only. Run locally (npx), it collects nothing — no accounts, no telemetry, no storage. The hosted mcp.tide.org endpoint records aggregate usage geography (approximate location only, never request content or tool arguments) to see where it's used. Full details in PRIVACY.md.
@tideorg/mcpSource: README.md at commit 1dcb29d
List all available content in the Tide agent pack by category
categoryrequiredRead a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)
namerequiredpartsectionRead a step-by-step playbook for a specific Tide task
namerequiredpartRead a composable skill definition
namerequiredpartsectionRead a reusable starter prompt from the pack
namerequiredRead an adapter instruction file (AGENTS, CLAUDE, replit)
namerequiredList all available scenario patterns under reference-apps/
Takes no parameters.
Read a scenario summary from reference-apps/<scenario>/scenario.md
namerequiredpartRead a scenario manifest from reference-apps/<scenario>/manifest.yaml
namerequiredRead a scenario role-policy matrix from reference-apps/<scenario>/role-policy-matrix.md
namerequiredRead a scenario bootstrap sequence from reference-apps/<scenario>/bootstrap-sequence.md
namerequiredMatch a user request to a known scenario pattern before falling back to generic playbooks
situationrequiredRecommend the right playbook for a given situation
situationrequiredAnalyze an EXISTING (possibly non-Tide) system for security gaps and map them to Tide capabilities. Returns the Security Analyst role instructions, the security gap mapping table (SG-01…SG-18), and the runtime-probe procedures. Use this when the user asks 'do a security analysis', 'where is my auth weak', or 'what would Tide change about my security'.
partinclude_runtime_probesRun a Blast Radius Assessment of an EXISTING app: an adversarial, vendor-neutral map of where authority is concentrated to a single point (whoever obtains that one thing obtains everything it governs), scored by blast radius (Total/Systemic/Contained/Limited) across three cores — Identity, Governance, Access — and delivered as a director-facing PDF. Phase 1 names no vendor; an opt-in Phase 2 companion explains how TideCloak shrinks each blast radius. Use this when the user wants to 'assess', 'red team', 'threat model', 'find the security gaps in', or make a before/after security case for an existing application.
partWhere TideCloak runs: local Docker vs partner-hosted (Skycloak managed TideCloak-as-a-service). Returns the local-vs-hosted decision with the honest trade-offs, the trust model, the verified Skycloak API reference (correct cluster field names and the required version), and the full provisioning playbook. CALL THIS BEFORE STARTING ANY TIDECLOAK DEPLOYMENT — the choice must be made up front (I-17) because a realm cannot be moved between local and hosted afterwards. Triggers: 'deploy to production', 'deploy TideCloak', 'go live', 'host this somewhere', 'managed option', 'stable URL', 'can someone host TideCloak for us', or any request to stand up an instance where local-vs-hosted has not been settled.
partReturns the exact command that installs `public/tide_dpop_auth.html` — the DPoP relay page the Tide enclave loads during login — plus its sha256, the required next.config.ts rewrite/CSP wiring, and how to verify. `@tidecloak/js` ships the file from 0.14.34; older SDKs and the TideCloak container do not, and a GitHub search finds a STALE copy that posts to window.parent, which breaks the popup fallback and fails login with TIDE-SWE-UNHANDLED. CALL THIS whenever DPoP is enabled (it is on by default), whenever a login fails with TIDE-SWE-UNHANDLED or 'Popup DPoP verification failed to load', and before copying this file from anywhere else.
Takes no parameters.
STOP KEYCLOAK'S 'UPDATE ACCOUNT INFORMATION' PAGE and collect the details in-app instead. Tide asserts ONLY a username (the vuid) -- no email, no name -- so Keycloak blocks new users on an unstyled form showing a 64-hex username. Returns: a read-only DIAGNOSTIC that identifies which of FOUR mechanisms is causing the page (they need different fixes), the script that fixes it, and a ready-to-drop React modal that collects the details AFTER login via the Account API. CALL THIS whenever signup, onboarding, 'Update Account Information', a profile/details form, or 'what users see after they create an account' comes up -- and ALSO proactively once a realm is bootstrapped, because the default is that every new user hits that page.
realmfieldsappNameframeworktidecloakUrlcomponentPathBRAND THE ENCLAVE FOR THE USER — generate a logo + background and upload them so the Tide login/approval screen is branded. Returns a single ready-to-run command that generates the assets (no image model needed), validates them, uploads both, and saves+signs the IdP settings. Also returns the VERIFIED upload contract (multipart parts, the png/jpg/jpeg/gif/webp allowlist with SVG REJECTED, the 5 MB cap, set-branding = save AND re-sign, IGA-exempt) plus image-model prompts for agents that can generate images. Pass realm/accent/appName to get the command pre-filled. CALL THIS whenever branding, a logo, a background, theming or 'skinning' the enclave or login screen comes up — then RUN the command; do not just describe it.
realmaccentappNametidecloakUrlSTART A NEW TIDE APP FROM A WORKING TEMPLATE. Returns the exact commands to copy a complete, building app — login, the DPoP page and its wiring, server-side token AND proof verification, and the realm bootstrap script — then install, bootstrap and check it. CALL THIS when building a new app, BEFORE writing any auth code: the code that most often goes wrong (provider config, DPoP, route and API protection) is then copied, not retyped. Pass `situation` and it picks the template; or name one. Not for adding Tide to an existing app.
appDirappNametemplatesituationFIND AND FIX WHAT IS WRONG WITH A TIDE APP, IN ONE COMMAND. Returns the command that checks an app for the faults behind most broken logins and unprotected APIs. It REPAIRS the mechanical ones itself (re-copies the DPoP page byte-exact, corrects a wrong rewrite path, gitignores .env) and prints the exact fix for the rest, which YOU apply — do not pass the list to the user. Covers: DPoP page missing/stale/served without its headers, useDPoP passed as a JSX prop (silently OFF), createTideCloakProxy called without protectedRoutes (protects nothing), adapter without its embedded key, remote JWKS, Bearer-only token parsing, no server-side verification, secrets about to be committed, a destructive change request pending. CALL THIS after scaffolding or changing auth code, BEFORE telling the user it works, and FIRST whenever a login or an API check misbehaves. This tool call itself only returns the command.
realmappDirappUrlcheckOnlyRead the gap register — what is still uncertain or unresolved in the pack
part90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
claude mcp add tide-pack -- npx -y @tideorg/mcp{ "mcpServers": { "tide-pack": { "command": "npx", "args": ["-y", "@tideorg/mcp"] } }}{ "mcpServers": { "tide-pack": { "command": "npx", "args": ["-y", "@tideorg/mcp"] } }}{ "mcpServers": { "tide": { "url": "https://mcp.tide.org/mcp" } }}{ "context_servers": { "tide": { "command": { "path": "npx", "args": ["-y", "@tideorg/mcp"] } } }}{ "mcpServers": { "tide": { "command": "npx", "args": ["-y", "@tideorg/mcp"] } }}{ "mcpServers": { "tide": { "url": "https://mcp.tide.org/mcp" } }}docker run -p 3000:3000 tideorg/mcpdocker build -t tideorg/mcp .docker run -p 3000:3000 tideorg/mcpdocker run -p 3000:3000 -e API_TOKEN=your-secret tideorg/mcp