Works with Claude, ChatGPT, Grok, Hermes, Meta Muse, Cursor and more. Sign in once. Your assistant can search, save, and tag your links. No API keys to copy.
Uncheck “Allow changes” when you connect and the assistant can look but not touch: search, list, read one link, list tags, get your overview stats, run a digest, and preview duplicates. Every write tool — save, edit, tag, delete, merge — refuses with a clear message.
Good for a shared assistant, a first try, or anyone who wants their crypt browsable but not editable.
Every client talks to the same endpoint: https://mcp.getlinkcrypt.com/mcp
https://mcp.getlinkcrypt.com/mcphttps://mcp.getlinkcrypt.com/mcpsearch and fetch to work. Write actions may be unavailable.search and fetch tools. Normal chat in developer mode can use every Link Crypt tool.search and fetch, that is now supported.Run this in your terminal:
claude mcp add --transport http linkcrypt https://mcp.getlinkcrypt.com/mcpThen run /mcp and follow the prompt to sign in and approve.
https://mcp.getlinkcrypt.com/mcphttps://mcp.getlinkcrypt.com/mcpCustom connectors are on Grok's paid tiers (SuperGrok and up). On Grok Business and Enterprise, an admin provisions the connector first.
Grok Build, xAI's terminal agent, reads the same MCP configuration as Claude Code, so a server added there carries over.
Run this in your terminal. It is the Hermes Agent from Nous Research.
hermes mcp add linkcrypt --url https://mcp.getlinkcrypt.com/mcpOn first connect Hermes prints an authorize URL, opens your browser to the Link Crypt sign-in, and waits for the callback on a local port. It caches the token under ~/.hermes/mcp-tokens/. Verify with hermes mcp test linkcrypt.
Running Hermes headless or as a gateway? Authorize once from an interactive terminal with hermes mcp login linkcrypt.
Hermes writes this to ~/.hermes/config.yaml:
mcp_servers:
linkcrypt:
url: "https://mcp.getlinkcrypt.com/mcp"
auth: oauthhttps://mcp.getlinkcrypt.com/mcpYou can also ask Muse in chat to add a custom connector for Link Crypt at that URL with OAuth.
Muse connects from Meta's cloud, so there is nothing to install. Meta does not review custom connectors. Disconnect any time under Settings → Connectors or in Link Crypt Preferences.
Add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"linkcrypt": {
"url": "https://mcp.getlinkcrypt.com/mcp"
}
}
}Add this to .vscode/mcp.json:
{
"servers": {
"linkcrypt": {
"type": "http",
"url": "https://mcp.getlinkcrypt.com/mcp"
}
}
}Add this to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"linkcrypt": {
"serverUrl": "https://mcp.getlinkcrypt.com/mcp"
}
}
}Run this in your terminal, then authenticate when prompted:
gemini mcp add --transport http linkcrypt https://mcp.getlinkcrypt.com/mcp16 tools, thin wrappers over the same REST API. Write tools need “Allow changes”; destructive ones always ask you to confirm.
| Tool | What it does | Kind |
|---|---|---|
| get_overview | Snapshot of your library: totals, growth, top tags and domains. | read |
| search_links | Full-text search across titles, descriptions, and saved page content. | read |
| list_links | List and filter links by tag, domain, favorite, or sort order. | read |
| get_link | Get one link’s full detail, including its tags. Pass detail: content for the full saved page text. | read |
| save_link | Save a new URL, with optional title, description, and tags. | write |
| update_link | Edit a link’s title, URL, description, or favorite/read status. | write |
| delete_link | Permanently delete a link. | write · confirm |
| list_tags | List every tag with its link count. | read |
| tag_link | Add or remove tags on a link. | write |
| update_tag | Rename, recolor, or redescribe a tag. | write |
| delete_tag | Delete a tag everywhere it’s used. | write · confirm |
| generate_digest | Cryptie-generated digest of themes and habits in your recent saves. | read |
| find_duplicates | Preview duplicate links or tags before touching anything. | read |
| merge_duplicates | Merge duplicate links or tags into their canonical copy. | write · confirm |
| search | ChatGPT-compatible alias of search_links: { query } in, { results: [{ id, title, url }] } out. Deep research uses this. | read |
| fetch | ChatGPT-compatible: { id } in, full saved record with the page text out. | read |
When you approve a connection you choose whether to check “Allow this assistant to make changes.” Leave it on for full read/write access, or turn it off for a read-only connection that can look but never save, edit, tag, or delete anything.
Every connected assistant shows up under Preferences → Connected AI assistants, with when it connected and when it was last used. Click Disconnect there, or disconnect from the client itself — either way, access is revoked immediately and the assistant needs a fresh sign-in and approval to reach your crypt again.
Tool inputs and outputs pass through whichever assistant you're using (Anthropic, OpenAI, xAI, Meta, Nous Research, or another vendor) the same way any tool call does. Link Crypt only sees the calls your assistant actually makes, same as a REST API key. Details in our privacy policy.
Prefer the REST API? Read the API docs →
https://mcp.getlinkcrypt.com/mcp. No trailing slash, no extra path.No. The MCP server is included with every plan and every trial, the same as the REST API.
Only if you allowed changes when you connected, and only when it asks you to confirm first. It never deletes anything as a side effect of another request.
Not directly — Obsidian doesn't speak MCP yet. See the Obsidian + AI guide for the pattern most people use instead.
A Link Crypt account with an active subscription or trial, and an MCP-capable client (Claude, ChatGPT, Grok, Hermes, Meta Muse, Cursor, VS Code, Windsurf, Gemini CLI, or anything else that speaks the standard remote MCP protocol). No API key to generate or paste.
They exist. Link Crypt provides search and fetch for ChatGPT deep research and company knowledge. Whether ChatGPT can also save, edit, or delete depends on your plan. Business, Enterprise and Edu workspaces can use every tool. On Plus and Pro, developer mode is a beta and connections are read-oriented, so write actions may be unavailable.
Yes. Ask for the full saved description or page text. The assistant uses fetch, or get_link with detail: content.