Integrations and partner program
CovaSyn is built as a hosted MCP server to fit into existing systems rather than replace them. This page shows what is connected today and what a partnership with your product can look like.
What is connected today
The CovaSyn MCP server speaks streamable HTTP and OAuth 2.1 with PKCE and dynamic client registration. Any MCP-capable client can connect; setup is documented for these clients:
Claude
Claude Code and Claude Desktop, connected via API key or OAuth. Step-by-step guide in the docs.
ChatGPT
Connected as an MCP connector through the OAuth consent flow, no manual key entry.
Cursor
Configured via mcp.json, documented in the setup guide.
VS Code
Configured via mcp.json, documented in the setup guide.
Official MCP registry
CovaSyn is listed in the official MCP registry as com.covasyn/chemistry. Aggregators and directories pick the entry up from there.
Who the partner program is for
ELN and LIMS vendors
Your users document in your system and compute in CovaSyn. An MCP integration brings structure analysis, property prediction and compliance tooling to where the data already lives.
Instrument vendors
NMR, MS, IR, UV: evaluation workflows that connect to your instrument data instead of adding another data silo.
Institutes and research groups
Joint formats, teaching and methods work. Coopetition welcome: we would rather integrate than duplicate.
Terms
We discuss terms in the partnership call, tailored to your product and sales structure. We deliberately do not publish flat rates.
Book a partnership call
45 minutes, via Teams or phone. You show us your product, we show you the integration, and afterwards both sides know whether a partnership holds.
Book a partnership call →