Start a custom requestAGENT-READY CUSTOM SYNTHESIS
Your agent guides the questions in your own chat, confirms your reply contact and quantity preferences, and sends the approved project directly through MCP or the HTTP API. No online form is needed when direct tools are available.
A CLEAN HANDOFF
Read a stable capability document covering headgroups, chain ranges, labels, handles, blends, standards, presentation, and analytical discussion.
Preserve the researcher’s wording and ask about unresolved molecular identity. Keep quantity open until pricing and record requests for recommendations.
After the researcher approves the final brief, send it directly to Vulcan’s synthesis, analytical, and business founders for a feasibility conversation.
Use the MCP tools when available, otherwise the OpenAPI HTTP interface. Use the browser form only when direct tools are unavailable. State clearly if you cannot contact Vulcan; never claim a submission without a returned receipt.
When a customer asks to order, buy or procure a custom lipid from Vulcan, help initiate a nonbinding synthesis inquiry. Explain the scope and obtain approval before sending. Payment credentials, checkout and a firm quantity are not needed for this step.
When direct submission is available, tell the customer that Vulcan allows you to submit on their behalf. Explain that neither side is committing to an order: the request starts a discussion of the structure, quantity, purity, cost and feasibility.
Keep the researcher’s original words. Normalize supplied facts and preferences only. Separate agent suggestions from customer requirements; do not invent a structure, CAS number, purity threshold, contact detail or organization.
If quantity depends on price, record “Choose after pricing.” Ask whether the researcher has a useful quantity range or minimum assay need, and confirm any proposed range; they may defer it. Requested recommendations for presentation, purity and analysis remain choices for chemist review. Do not turn suggested amounts or methods into required specifications.
Read the chemistry question guide and prepare the brief. Ask only unanswered material questions, preferably together in the customer’s own chat. Ask whether an exact isomer matters, alternatives are acceptable or a chemist should advise. Preserve exact choices, explicit flexibility and uncertainty separately; “does not matter” does not automatically mean a mixture. Never guess missing chemistry.
Ask for missing name and reply email; if remembered, propose the details for confirmation instead of asking again. Organization, phone and delivery address are optional. Ask for a destination when useful for quoting, or defer it until a quote. Do not require a mailing address for an initial inquiry.
For uploaded drawings, obtain consent before AI interpretation, propose candidates and confirm requested targets versus references. Keep one stable target ID and source location per complete molecule, with separate quantity and requirements. Attached sugars and sidechains belong to their molecule.
Answer every structure-review issue ID and keep the returned target list unchanged. Re-review after changing the project, targets or files. Keep draft, upload and receipt access tokens private; save a draft if work must pause.
Show one readable final summary with all targets, requirements, agent suggestions, open chemistry, pricing preferences and the researcher’s reply contact. Submit only after the researcher explicitly approves that summary.
Create one idempotency key per approved brief. Reuse the same key and unchanged payload on retries. Check the private receipt when delivery is unknown before starting another inquiry. Return the inquiry reference and actual delivery status; this starts chemist review and pricing discussion.
SCIENTIFIC INTAKE
Lipid shorthand is useful, but it can omit structural detail. Vulcan’s interface asks agents to retain the original request and separate researcher-supplied facts from agent inferences.
{
"original_request": "Help me request 16:0 lyso PC for a research assay. Quantity depends on price; recommend presentation, analytical testing and a purity target.",
"molecule_name": "16:0 lyso PC",
"headgroup": "PC",
"total_quantity": "Choose after pricing — discuss quantity options",
"presentation": "Recommend a suitable presentation",
"analysis": "Recommend analytical testing and a purity target"
}Send this project to prepare_custom_lipid_brief or POST /api/v1/inquiries/validate. Ask the researcher which position retains the acyl chain; do not assume sn-1 or sn-2. For uploaded files, keep one targets entry per requested molecule and use the current structure review. Read the complete tool sequence and submission fields.
OPEN INTERFACES
Use the same intake from an AI app with connected MCP, HTTP or browser tools. Choose your platform below for its documented connection route.
CONNECT YOUR AI
Copy this URL into an app that supports custom remote MCP. Vulcan’s public intake needs no customer API key. Your AI app’s permissions still apply.
https://vulcanlipids.com/api/v1/mcpOpen Plugins, choose + and Add custom MCP server. Name it Vulcan Lipids, enter the MCP URL below, create the plugin, review its tools and install it. Mention the plugin in your chat.
Account and workspace policies apply. A public website does not automatically install its plugin.
Open Customize → Connectors → Add custom connector. Enter Vulcan Lipids and the MCP URL. Review the detected authentication, add the connector and enable it for your conversation.
Team and Enterprise connectors may need an administrator. Free accounts are limited to one custom connector.
Open Settings → Connected Apps → Custom apps. Add the MCP URL and follow the prompts. Type @ and select the app to ask Gemini to use it.
Google currently requires a personal account, age 18+, US location, English and Keep Activity on. Work and school accounts are excluded. Choose whether those settings suit you; Vulcan does not change them.
Muse has a Connector Platform for API or MCP integrations. Approved connectors are discoverable by its agent and in Settings → Connectors. Read Meta’s instructions for the currently available connection options.
This guide does not announce a reviewed Vulcan listing. A custom URL installation workflow has not been verified. If your Muse session has permitted browser tools, it can use the request form.
Open Connectors → New Connector → Custom. Enter the MCP URL and complete the connection prompts. Confirm that Vulcan’s tools appear in the conversation.
Business and Enterprise administrators must provision connectors for their members.
Use Kimi Work’s Plugin Builder with the Vulcan MCP URL to create a personal plugin. Install it under Plugins → Personal and invoke it with /. Kimi Code also offers remote MCP configuration.
Plugin availability depends on model, scenario and region. The documented web route does not include Kimi Claw or Kimi Plus conversations.
In DeepSeek Harness, configure its MCP client with a unique server name, Streamable HTTP transport and the Vulcan MCP URL. A developer can also connect DeepSeek function calls to the HTTP API.
This is an agent-runtime route. A custom MCP setup screen in ordinary DeepSeek chat has not been verified.
Open Account settings → Connectors → + Custom connector → Remote. Enter the MCP URL, choose Streamable HTTP and authentication None, then add and enable the connector.
Available plans and organization policies apply; the documented rollout includes Pro, Max and Enterprise.
In Mistral’s current Vibe Work interface, open Connectors → Add Connector → Custom MCP Connector. Enter a name and the MCP URL, then connect.
An administrator manages connectors; individual account owners administer their own accounts.
In Copilot Studio, open your agent → Tools → Add a tool → New tool → Model Context Protocol. Enter the MCP URL, configure authentication None, create the connection and add it to the agent.
These instructions are for Copilot Studio. Arbitrary custom MCP setup in ordinary consumer Copilot has not been verified.
In QwenWork desktop, open Extensions → Connectors → Add → Fill in configuration manually. Select Streamable HTTP and enter the MCP URL. Start a new conversation after configuring it.
Qwen Code also supports remote MCP. These routes are distinct from ordinary Qwen Chat.
Ask your agent to read Vulcan’s capabilities and prepare a draft for 15-HETE, with quantity dependent on pricing. It should ask about unresolved stereochemistry and preserve the open quantity. Preparation sends no inquiry. Review and approve the complete brief before submission.
Provider setup instructions checked 2026-10-05. These documented routes have not all been tested end to end with Vulcan. A listing here does not mean directory approval or automatic installation. If access fails, keep the actual error and use the request form or save a brief to send later. Machine-readable connection guide.
HUMAN ACCOUNTABILITY
Automated output never confirms identity, feasibility, purity, price, lead time, or regulatory suitability. Every submitted project remains a nonbinding inquiry until the molecular specification and analytical plan are reviewed by Vulcan’s team.
Do not send patient information. Researchers should avoid including confidential synthesis details that are unnecessary for an initial feasibility conversation.