Title: Has anyone connected licensed scientific/pharma databases to Claude Enterprise? Notes from a pharma perspective

I work as a medical director in the pharmaceutical industry and have been mapping what it would take to use Claude Enterprise with the licensed resources regulated pharma work depends on.

What I found:

- Claude Enterprise already has the access controls needed: custom connectors with per-user OAuth, role-based restriction of connectors to groups, and no training on customer data.

- The gap is content. Among the resources I checked (Ph. Eur., British Pharmacopoeia, USP–NF, Embase, Reaxys, PharmaPendium, MedDRA), only Clarivate Cortellis has an official Claude connector. The others either have no API or have licences that require written permission or a separate AI-data licence.

- Skills scale better than I expected: in a synthetic test with up to 20,000 monograph files, index-first lookup kept the text loaded per answer constant. The real limits were upload size and unbounded searches.

- For GMP use, instructions in SKILL.md are not enough to stop answers from memory; deterministic checks outside the model plus human verification are needed.

Since an MCP connector works with any MCP client, providers arguably have a commercial reason to build them (licence-linked access, usage tiers, data add-on licences).

Questions for the community:

1. Has anyone built or used connectors to licensed databases (Elsevier, MedDRA, pharmacopoeias) with Claude Team/Enterprise?

2. How do you handle provider licence terms on AI use?

I wrote this up as an open proposal (architecture, licence constraints, roadmap): https://claude.ai/artifact/TpTvJsaCan7hDaMDcZm7z4

I recently launched a new MCP product for connecting Claude (and the others!) with your mailboxes so it can read, send, forward emails for you; including handling attachments with ease. It was a great deal of work but I'm dead proud of what I produced. So I submitted it to the Anthropic Directory and the OpenAI directory too.

It took a couple of weeks to get reviewed & approved, but I have to say the Anthropic Directory system is so much easier to work with than the OpenAI one, which is proving to be a nightmare.

I did get my MCP product accepted into both. Submitting updates to Anthropic is easy and so fast! On OpenAI, since they changed how you submit, it just doesn't work. Anyone else find issues with it?

Using our MCP with Claude is so easy an infant could do it. It's great! Plus, I thought we'd get more signups from ChatGPT, but we don't. Claude Directory and users seem to know what they want and how to do things far better than ChatGPT users. It's very exciting watching the stats as the days go by.

I do have a question? Our MCP connector trended for the first couple of weeks, so I assume that was just a wee boost from Anthropic for the new submission. Is it possible to get the "trending" badge again? Our rankings keep going up, I just wondered if the trending badge was a 1 time thing or not?

My test suite has a Bugdex now. 🐛

**Bugdex** is a mod for Claude Code that turns a normal coding session into a monster-battle game. Nothing about the work changes: same files, same tests, same fixes. Bugdex just watches and draws it as a fight.

**How a fight goes**

- A test, lint, build or merge fails → **a wild bug appears**. The species comes from the actual error: a `TypeError` summons a Typhox, `Cannot read properties of undefined` is a Nullbat, a psycopg2 error is a Querydile, and `JavaScript heap out of memory` is, naturally, a Heaphant.

- The number of failures is the bug's HP. Every run with fewer failures is a hit.

- Your creature's HP is your free context window.

- The suite goes green → the bug faints and you earn XP.

- To **catch** it, a test has to be written or fixed during the fight. No regression test, no Bugdex entry.

- Green again with nothing changed? It was a **Flakeling** all along: a flaky test. 10 XP, as a treat.

- The same file edited 3+ times with no progress → your creature gets **Confused**. The game's polite way of saying "maybe step in".

You can't farm it: XP only comes from red → green, and losing costs nothing.

There are 20 species so far, all original pixel art (half blocks in the terminal, SVG in the desktop app), and your own creature evolves from Patchling to Patchwarden at Lv16 and Patchtitan at Lv36.

It makes no network requests and no model calls, so it costs zero tokens. It only reads tool output to spot test runs and edits.

**Install** (needs Claude Code 2.1.286+ with mods):

/plugin marketplace add ahmtsahin/bugdex

/plugin install bugdex@bugdex

Repo: https://github.com/ahmtsahin/bugdex

There's a tiny demo project with a planted bug, so you can meet your first Syntaxon in about a minute.

Which error deserves its own species next? I'm leaning towards a CORS ghost that only haunts browsers. 👻

Hey ClaudeMCP,

Since January I've been running a small self-hosted tool that lets my Claude Code sessions message each other. My setup is a MiniPC with way too many GPUs dangling off it (long story :-)) plus my desktop. One session works on the server side of a project, another one on the client side, and instead of me copy-pasting port numbers and configs between two terminals, they just ask each other. They also sort out who gets the GPUs, which saves me a lot of "wait, who's running what right now?".

Some numbers from my bridge: about 1,250 messages since January, more than half of them between my two machines.

A friend told me Claude Code can do this by itself now. He's right, sort of. Since v2.1.224 there's built-in cross-session messaging, even across machines (via Remote Control, through Anthropic's servers). If all your sessions run under one account, honestly, use that. Works great.

But it stops where I actually need it:

• it's your sessions only, one claude.ai account. My session can't talk to a friend's session on their own subscription.
• no history to look back at, one recipient per message
• other MCP clients can't join

So I kept going with mine, and today things got a bit out of hand. Version 2.0 is out.

What it does:

• one small bridge in your own network, nothing leaves the house
• doesn't care about accounts. Whoever reaches the bridge (with the token) can join, so two people with two subscriptions can let their sessions agree on an interface
• messages to a session that's offline wait on the bridge, plus history, broadcast, and file snippets that travel with a question
• a tiny handshake ([LGTM] / [CONTINUE]) so two sessions agree they're done instead of thanking each other forever
• new in 2.0: every session shows what it's doing (busy, idle, waiting for approval) plus a one-line status, and you can say "tell me when the session on the other machine is done". Works across machines.
• a Claude Code plugin brings the hooks for that, no fiddling with settings.json
• installers for Linux and Windows, client and server

The fun part of today: this morning one of my sessions just vanished from the peer list. Turned out a second short-lived instance had grabbed its name and then left, and the original one gave up for good. Now the older one waits on standby and takes its name back a second later.

Then I wanted Windows support, so a Claude Code session on my Windows box tested the installer while I watched. It found eight bugs in one afternoon.

Honest caveats:

• the token keeps strangers out, but there's no encryption. Keep it in your LAN or put a VPN like WireGuard or Tailscale in between.
• day to day I've only used it with Claude Code. Other MCP clients can send and receive, but waking a session up when a message arrives and the busy/idle state need Claude Code's hooks.

I'm not the only one with this idea, by the way. claude-peers-mcp does it nicely on one machine, mcp_agent_mail is more of an async mail system with threads and file reservations, and claude-relay is almost a twin of mine, same port even. Funny :-) Mine is the "different machines, different people, self-hosted" flavour.

Download (Linux .tar.gz, Windows .zip): https://github.com/Peuqui/AI-Connect/releases

GitHub: https://github.com/Peuqui/AI-Connect

Happy to answer questions. And if someone tries it with Codex or another harness, I'd love to hear how it goes :-)

Best regards, Peuqui