Commercializer
ai.commercializerPublished by commercializer.aiOfficial publisherv1.3.2Updated Nov 3, 2026
Commercial strategy for medical device and life-science companies, read from the governed registers.
Overview
Remote Commercializer server that lets an assistant read governed medical-device and life-science registers and run commercial strategy workflows with…
- What you can do
- Read regulatory and market registers: FDA clearances, EU and other registrations, recalls, adverse events, trials, patents, clinician payments, tenders and filings, each answer carrying a citable read id
- Look up a company's footprint, profile and device history, and compare companies across registers
- Keep, recall and forget findings on a company profile, and search or fetch profiles
- Run one of 48 named tools for a single question, such as a US pathway or freedom-to-operate screen
- Start and follow 33 workflows, answering checkpoints, and ask the Commercializer agent questions
- When to use it
- Useful for medical device and life-science teams that want an assistant to answer regulatory and commercial questions from official registers, with every record cited, or to run pathway, submission, market entry and competitor workflows inside their own workspace.
- Requirements
- A remote Streamable HTTP endpoint; no local package. Sign-in is OAuth 2.1, or an API key sent as an Authorization Bearer header for scripts. A Commercializer account and workspace are needed, and workflow runs and research count against the workspace plan.
Installation
In SourceWeft
- Open Commercializer in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
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/ai.commercializer%2Fcommercializer/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"commercializer": {
"type": "http",
"url": "https://commercializer.ai/mcp"
}
}
}README
Commercializer
Commercial strategy for medical device and life-science companies, read from the governed registers.
Bring it into the AI assistant you already use.
[Add to VS Code] [Add to Cursor] [Add to Claude] [Add to ChatGPT]
Connected, your assistant works on your company the way the Commercializer app does. It reads the governed registers (FDA clearances and approvals, EU and other registrations, recalls and adverse event reports, registered trials, patents, payments to clinicians, public tenders and company filings), cites every record it uses, keeps the findings worth remembering on your company's profile, and runs workflows that deliver a pathway decision, a submission checklist, a market entry plan, a competitor footprint or a company brief, asking you at each decision.
Everything it does happens as you, in the workspace you choose, and is listed on the MCP page of your workspace under its name, where you can disconnect it at any time.
- The server:
https://commercializer.ai/mcp(Streamable HTTP; sign in with OAuth 2.1, or use an API key). - This repository:
github.com/Commercializer-ai/commercializer-mcp, the plugin and a guide for every assistant. - The page: commercializer.ai/product/assistant.
- Let the assistant set itself up: give it
https://commercializer.ai/mcp/llms.txt. It says how to connect from each client, how to sign in, how to work the workspace and every tool.
Connect your assistant
Signed in to Commercializer, the MCP page of your workspace walks the same steps for the assistant you pick and makes an API key when you need one.
The plugin
This repository is also a plugin: the server, a skill that teaches the assistant how to work the workspace (read before stating a figure, cite every read, keep findings, use the tools, run workflows), and five skills you can call by name.
It follows the open Agent Plugins format (plugin.json, mcp.json, skills/) that
ChatGPT, Codex, GitHub Copilot, VS Code and Cursor read, and carries a Claude Code manifest (.claude-plugin/) beside it.
It is also listed in the MCP Registry as ai.commercializer/commercializer.
What it can do
Every tool, with what it reads or changes. In short:
- Read the registers:
resolve,company_footprint,company_profile,device_trace,graph_compare,lookup,trials_find,recalls_find,document_search,document_get, and every other register throughlist_registersandread_register(EU, Canada, Australia, China, Japan, Korea, tenders, Medicare, hospitals, patents, filings). Every answer starts with a read id you can cite. - Know your company:
search,fetch,list_profiles,get_profile,recall_findings,keep_finding,forget_finding. - Answer one question with a tool:
list_tools,run_tool,get_tool_run; 44 tools, from a US pathway and an FTO screen to open tenders, a trial landscape and who is investing in your space. - Run workflows and watches:
list_workflows,start_workflow,get_workflow_run,answer_checkpointand more; 29 workflows across regulatory, commercial, evidence, innovation, capital and programme work. - Ask the agent:
ask_agent,get_agent_answer.
Try:
- What clearances and recalls does our closest competitor hold, register by register?
- Which US pathway fits our device, and which predicates would we lean on?
- Run a market entry workflow for Germany and the UK on our lead product.
Privacy and control
- It works as you, in the one workspace you approved, and can do only what you can do there.
- Every read, finding and run it makes is marked with its name on the MCP page and on the profile.
- Disconnect an assistant or revoke a key on the MCP page; it stops at once.
- Workflow runs and research count against your workspace's plan, as the app's own do.
More in Security and data. Problems: Troubleshooting.
Support
commercializer.ai/contact · [email protected] · Privacy · Terms
Source: README.md at commit ebcdbe7
Tools
0Version history
4- v1.3.2LatestNov 3, 2026
- v1.3.1Nov 1, 2026
- v1.3.0Oct 29, 2026
- v1.1.1Oct 26, 2026
Score
75% 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.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.