Start now

Connect alkemy to your AI assistant

Last updated October 10, 2026

Work where you already are. The alkemy connector lets your AI assistant — Claude, Claude Code, ChatGPT, Codex, Cursor, or GitHub Copilot / VS Code — read your Key Accounts and search your network, so you can ask about an account or get briefed for a meeting without ever leaving the chat. If you allow it, your assistant can also save what it learns back to alkemy.

What you can do

Once it's connected, ask your assistant in plain language:

  • Find accounts — "what Key Accounts do I have?", "find Acme".
  • Get a brief — "brief me on Acme", "what should I know before I meet them?" — you get the account's pre-meeting brief.
  • See what's open — "any burning issues at Acme?", "what should I raise in the meeting?".
  • Meeting prep — "who's in the room for the Acme meeting?", "talking points for Acme".
  • Search your network — "who do I know at Acme?".
  • Switch workspace — "switch to my Northwind workspace".
  • Read saved calls — "what did we agree on the last Acme call?", "what action items are open this week?".

What writing can do

Rolling out: writing is turning on in stages. The consent screen shows the write permissions only where writing is on. Where it is off, your assistant can only read.

When you allow writing on the consent screen, your assistant can also:

  • Save a call — paste a transcript or meeting notes and say "save this call to alkemy". Your assistant reads it with its own AI and saves the summary, the attendees, burning issues, signals and action items to the Key Account. The call shows on the account's Calls tab.
  • Track action items — add a follow-up with an owner and a due date, and mark it done or dropped later.
  • Create a Key Account — your assistant shows you the company first and creates the account only after you confirm. A new Key Account turns on weekly research, which uses alkemy credits.
  • Update the account — add or resolve a burning issue, add a signal, and add or update a person.
  • Import your LinkedIn network — send your LinkedIn export (the ZIP or Connections.csv). A new import replaces the one before it. Every import can use credits: alkemy runs a web search for each missing profile link, and enriches the people in your file who match people at your Key Accounts. alkemy also enriches your first import automatically, which uses credits.
  • Enrich your network — look up full profiles for the people in your network. Enrichment uses alkemy credits and stops when your credits run out.

The connector can't delete an account, a person, a signal or a source. Your assistant uses its own AI plan, so reading and saving use no alkemy credits. Three things do: enrichment, the weekly research on a new Key Account, and imports. An import uses credits to find missing profile links and to enrich the people it matches at your Key Accounts.

What you'll need

  • An alkemy account that belongs to at least one workspace.
  • A supported assistant: Claude (web or desktop), Claude Code, ChatGPT (with Developer Mode enabled), Codex, Cursor, or GitHub Copilot / VS Code.

Connect it

The connector address is:

https://api.alkemyos.com/api/mcp

Find your connector URL in Settings → Connectors in alkemy. That page also has step-by-step setup for each assistant, with commands you can copy.

Add it in your assistant:

  • Claude — Settings → Connectors → Add custom connector, then paste the address.
  • Claude Code — run claude mcp add --transport http alkemy <connector URL>, then run /mcp and choose alkemy to sign in.
  • ChatGPT — turn on Developer Mode, then add the address as a connector.
  • Codex — run codex mcp add alkemy --url <connector URL>, then codex mcp login alkemy to sign in.
  • Cursor — Settings → MCP → Add new MCP server, then paste the address.
  • GitHub Copilot / VS Code — add it as an MCP server.

Then finish signing in:

  1. Your browser opens alkemy's own sign-in page — log in exactly as you normally do. There's no separate password for the connector.
  2. Review the consent screen — it shows what the assistant will be able to see, and what it can save if it asked to write. Turn off any write permission you don't want.
  3. Pick the workspace you want to connect (if you belong to more than one).
  4. Approve — and you're connected.

⏱️ What to expect: the whole thing takes under a minute, and you only do it once per assistant.

Switching workspaces

Connected to the wrong workspace? Just ask to switch by name — for example, "switch to Northwind" — and everything you ask afterward returns that workspace's accounts. Not sure where you are? Ask "which workspace am I in?".

Permissions

  • Read — your assistant always gets read access: your Key Accounts, saved calls and action items, your network, and your workspaces. Settings → Connectors shows it as Read accounts and network.
  • Write — your assistant can ask for two write permissions. Each one is a switch on the consent screen, and you can turn it off. Writing is rolling out, so the switches show only where writing is on.
  • Key Accounts (write) — saves calls, action items, signals and people, and can create new Key Accounts. Settings → Connectors shows it as Save to Key Accounts.
  • LinkedIn network (write) — imports your LinkedIn export and enriches it. Settings → Connectors shows it as Import and enrich network.
  • To change permissions — disconnect the assistant and connect it again, then choose again on the consent screen.
  • To see what an assistant can do — open Settings → Connectors. Each connected assistant shows its permissions.

Privacy & access

  • No deletes — the connector can't delete an account, a person, a signal or a source in alkemy.
  • Scoped to one workspace at a time — the one you pick when you connect, switchable whenever you like.
  • Only what you can see — the connector respects your existing permissions. Accounts you can't open in alkemy stay hidden here too.
  • Your normal login — it uses alkemy's own sign-in, so there's no extra password to manage.
  • To disconnect — in alkemy: Settings → Connectors → Disconnect, or remove it in your assistant.

Troubleshooting

  • "That account isn't part of any workspace." You signed in with an account that isn't in an alkemy workspace. Sign in with the account your team uses.
  • The sign-in page expired. The connect window stays open for about 10 minutes — if you took longer, start the connection again from your assistant.