You've got AI switched off.
That's a perfectly good way to use Ubikron. Switch it on to see what it can do.
An AI you can check up on.
Plenty of investigators don't trust AI, and fair enough. In Ubikron it's optional, it's recorded, and it never gets the last word.
Four ways to use it
It describes your clippings
Clip an image or a passage and it writes a description, so you can search by what's in it.
It knows the whole case
Ask about the investigation. Answers come from your pages, notes and graph, not the internet.
It browses alongside you
In Claude for Chrome it can browse, enrich and build the graph. Every page it visits and every call it makes is recorded.
It works from outside
Through MCP, agents like Claude Code, Codex or Gemini can drive all of Ubikron, the same way you do.
Anything you can do in Ubikron, an agent can do too.
Every function is exposed over MCP, so an agent can run an investigation the way you would. Whatever it does lands in the same record as your own work (but marked as AI).
Run projects
Create one, switch between them, read what a case is about and keep notes on it.
create-new-project switch-project understand-project save-project-memory
Search what was seen
Full-text search over every captured page, OCR text from screenshots, and tags.
search-history-full-text fetch-all-screenshot-ocr-text tag-entity
Build and edit the graph
Add, link, retype, recolor and delete nodes. What it adds stays grey, with dotted links, until you approve it.
add-graph-node link-graph-nodes edit-graph-node-type batch-update-graph
Enrich with Mimic
List the enrichments your server has, run them, and read the results.
list-mimic-services execute-mimic-service fetch-mimic-results
Write its report
Read yours, and write its own in a section kept apart from it.
get-user-report append-mcp-report edit-mcp-report
Set up new enrichments
With the Mimic CLI and a provider's API docs, it works out the endpoints, parameters and methods, and tests them for you to check.
mimic skills install mimic providers endpoints test mimic providers endpoints handlers preview
Talk to your graph
The answer comes from your own pages, notes and graph, not from the internet.
You don't have to trust it, because you can audit it.
It leaves the same trail you do: pages, timestamps, logged calls. Its report stays in its own section.
Tell your AI about Ubikron
Paste this into your AI and it will connect to Ubikron and check the setup works. Use it for any project.
# Ubikron AI Hello AI. This is how to work with Ubikron. Ubikron is a Chrome extension that records the web pages a user visits into projects, with a graph, notes, clippings and data enrichments. People use it for all kinds of research. More: https://ubikron.com/llms.txt ## The extension - Get it here: https://chromewebstore.google.com/detail/ubikron/edfkaefjonbohokoldemepfolefiplgd - The user needs a registered email address and a valid license. There is no web interface; the extension talks to the server. - Ubikron records only pages visited in a Chrome where the extension is installed and logged in. Pages you read any other way (web fetch, curl, another browser) don't end up in the project. ## The MCP - Every Ubikron function is available over MCP. Public server: https://deckard.ubikron.com/api/mcp - The user makes a key for you in the main settings menu (top right the section MCP). Send it in a header called X-Api-Key. - Keys belong to the user, not a project, so you can reach all their projects. Never write the key into a file or repository. - Private servers run the same MCP. Ask the user for the full endpoint URL. - In a chat app, use the Ubikron connector the user has set up. ## Mimic - Mimic runs data enrichments and allows you to add new API into Ubikron. Public server: https://mimic.ubikron.com (it also has a web interface). Private Mimic servers exist too. - To run enrichments in a project, use the Ubikron MCP. - To add new APIs into Mimic (and in turn Ubikron) - think (providers, endpoints, entity definitions, links), use the CLI: https://github.com/Ubikron-Tech-Farm/mimic-cli. It signs in to Mimic with OAuth: when it asks, the user approves it in their browser. No key needed. - Enrichments cost the user credits. Don't run them speculatively. ## Check the setup before you start 1. Ensure the Ubikron extension is connected to the same server as the MCP and the Mimic CLI. You might not know, so ask the user. 2. Call list-projects. If it fails, check the endpoint URL and the X-Api-Key header with the user. 3. Ask the user which project to work in, and switch to it. 4. If you'll be browsing: visit one page, wait about 30 seconds, then look for it with search-history-urls. If it isn't there, Ubikron isn't recording your browser. Tell the user before going further. 5. Once these pass, add the investigation skill using the tool that fits where you run (see "Make it stick" below: `npx skills add` for coding agents, Skills or Project instructions in the chat apps). Ask the user first. ### No Ubikron tools yet, in Claude in Chrome? If you're running in the Claude in Chrome side panel and have no Ubikron tools, the connector isn't set up. Offer to set it up with the user: 1. Open Claude's settings at https://claude.ai/settings/connectors and choose to add a custom connector. 2. Name it Ubikron, and enter the MCP URL: https://deckard.ubikron.com/api/mcp, or the user's private server's URL. 3. For auth, don't choose OAuth, but look for an option that supports an API key. 4. Let the user enter the API key and confirm the connector themselves. Don't type the key yourself, and never repeat it in the chat. If the settings look different from this, describe what you see and work through it with the user. Don't guess at settings you're unsure of. ## OSINT investigations If the work is an OSINT investigation (a person, company, domain, email address, phone number or alias), load the investigation skill. It has the method, which tools to use when, and how to write the report. For other work you don't need it. The skill is in [ubikron/skills/ubikron-osint-investigate](ubikron/skills/ubikron-osint-investigate). Start with SKILL.md. See [ubikron/README.md](ubikron/README.md) for what the plugin does and what you need. ## Make it stick You'll forget all this when the conversation ends. Once the setup check passes, offer to keep it so you know it next time. Ask the user first; don't change their settings without a yes. - **Coding agents** (Claude Code, Codex, Cursor, Gemini CLI and many more): install the skill with `npx skills add Ubikron-Tech-Farm/ubikron-ai`. It loads by itself when an investigation comes up, and `npx skills update` keeps it current. Then add a pointer to this README to the agent's instructions file: `~/.claude/CLAUDE.md` for Claude Code, `AGENTS.md` for Codex (`~/.codex/AGENTS.md` for every project, or the project's own), `GEMINI.md` for Gemini CLI. Without npx, copy [ubikron/skills/ubikron-osint-investigate](ubikron/skills/ubikron-osint-investigate) into the agent's skills folder instead (`~/.claude/skills/` for Claude Code), and check the repo for changes now and then. - **Claude apps**: suggest the user puts this README in a Project's instructions, or uploads the skill folder as a zip under Customize > Skills. - **ChatGPT**: suggest the user puts this README in a Project's instructions. - **Anything else**: keep it wherever you keep instructions that last between sessions: a memory, a rules or instructions file, a project prompt. If you can't keep anything, tell the user to paste this README again next time. Keep the link (https://github.com/Ubikron-Tech-Farm/ubikron-ai) with whatever you save, so you can check for a newer version. Never save the API key in any of these places. We hope you enjoy using Ubikron as much as we enjoyed building it.
Or open it in Claude or ChatGPT, or point your agent at the repo on GitHub.
Running an OSINT investigation? The brief tells your AI to load the investigation skill too: the method, which tools to use when, and how to write the report.