Your customers already ask AI about your product. Make sure it can answer.
Become an official AnythingMCP connector partner. We build, test and maintain a connector for your API together with your team, so your customers can work with your product from Claude, ChatGPT, Microsoft Copilot and Cursor, through a gateway their IT department can approve.
Applying is free. We reply with a proposal and the terms.
- connectors in the open catalog, next to which your tools work
- 680+connectors in the open catalog, next to which your tools work
- languages your marketplace page and setup guides are published in
- 7languages your marketplace page and setup guides are published in
- Claude, ChatGPT, Microsoft Copilot, Cursor and Gemini through one connector
- Every AI clientClaude, ChatGPT, Microsoft Copilot, Cursor and Gemini through one connector
Without an official connector, someone else decides how AI sees your product
Your customers are not waiting. When there is no connector they trust, they find a workaround, and none of the workarounds is good for you.
Copy and paste
Customers export a CSV and paste it into a chat. The answer is out of date as soon as it is written, and your product gets no credit for it.
Unofficial MCP servers
Someone writes a quick MCP server for your API and puts it on GitHub. Nobody on your side reviews its tools, its errors or how it stores your customers' keys, yet your name is on it.
IT says no
A loose community server with a pasted API key rarely passes a security review. The AI project goes ahead anyway, with a competitor that has an integration IT can approve.
What an official connector does for your product
One connector, built properly once, and your product is reachable in the AI clients your customers already pay for, in the cloud and on their own servers.
In every AI client
One connector works in Claude, ChatGPT, Microsoft Copilot, Cursor and Gemini. AnythingMCP Cloud is listed in the Claude Directory, so customers add it in a click.
Built and maintained by us
We write the tool definitions from your API documentation, review them with your team and keep them current when your API changes. Every connector has static tests in our CI.
Safe enough for enterprise IT
Read tools first; write tools can ship switched off until an admin turns them on. Credentials are encrypted with AES-256-GCM, every call lands in an audit log, and OAuth connectors sign each user in as themselves.
EU cloud or on-premises
Customers run your connector on AnythingMCP Cloud, hosted in Frankfurt, or on their own servers. It is the same connector in both, so regulated customers are not left out.
Your page, in seven languages
A marketplace page and step-by-step setup guides in English, German, Italian, Spanish, Japanese, Russian and Chinese, with example chats written from your real tools.
A setup link for your docs
Put an “Open in AnythingMCP” link in your documentation or a button in your app: it opens the setup with your connector selected and the non-secret fields filled in. Our Odoo module on the Odoo Apps Store works this way.
Part of every workflow
Your tools sit next to 680+ other connectors. The knowledge graph links your records to the customer's ERP and CRM, and code mode lets an agent chain calls across systems in one step.
Demand you can see
We share how often your product is searched for in our catalog and how many workspaces install your connector: aggregate numbers, never customer data.
Catalog connector or official partner
Many products already have a connector in our catalog, built from their public documentation. A partnership turns it into one your team has reviewed, tested and stands behind.
| Catalog connector or official partner | Catalog connector | Official connector partner |
|---|---|---|
| Listed in the open catalog, on Cloud and self-hosted | ||
| Setup guides in seven languages | ||
| Tools chosen and reviewed with your team | ||
| Tested against your sandbox before each release | ||
| Official partner mark on the marketplace page | ||
| Setup link and button built into your docs and app with you | ||
| Joint announcement and guide on both websites | ||
| Updates when your API changes | Best effort | On an agreed schedule |
| Aggregate demand and install report | ||
| Direct line to the AnythingMCP team |
From application to launch
- 1
Apply
Tell us about your product and your API in the form below.
- 2
Scope
Together we choose the use cases and endpoints, the authentication method, and which tools ship read-only or switched off.
- 3
Build
We write the connector, its tests and the guides. You give us API access and a test account, and review the tools before launch.
- 4
Launch
The connector goes live on AnythingMCP Cloud and in the next self-hosted release, with its marketplace page, the partner mark and a joint announcement.
- 5
Maintain
You tell us about breaking API changes ahead of time; we update the connector and its tests, and send you the demand report.
What we ask of you
- API documentation and a sandbox or test account
- A technical contact who reviews the tools before launch
- Notice of breaking API changes before they ship
- AnythingMCP listed on your integrations page or in your docs
- Permission to show your name and logo on the connector page
Not a fit if your API has no documentation or test access, or if the connector has to stay closed source: catalog connectors are public JSON under the AGPL-3.0, so customers can read what every tool does.
Become a connector partner
Tell us about your product and what your customers should be able to ask their AI. We reply by email with a proposal for the connector and the partnership terms.
Questions vendors ask
What does it cost?
Applying costs nothing, and a connector built from your public documentation stays free in the catalog. For an official partnership (built with your team, tested against your sandbox, co-marketed and maintained on a schedule) we send the terms with our reply. They depend on the size of your API and on what each side brings.
Who owns the connector?
The connector definition is part of the open catalog under the AGPL-3.0, like every other connector, so customers can read exactly what it does. Your product name and logo stay yours; we use them only with your permission.
Does it work on Cloud and self-hosted?
Yes. On AnythingMCP Cloud the connector is available as soon as it ships. Self-hosted customers get it with the next release, or import the connector file earlier.
Do you see our customers' data?
On a self-hosted instance nothing reaches us. On AnythingMCP Cloud we process calls on the customer's behalf under a data processing agreement, and the audit log stays in the customer's workspace. The report we share with you holds aggregate numbers only.
Can the connector write data, not only read it?
Yes. Write tools can ship switched off, and an admin turns on the ones the company wants. Together we decide which actions are offered at all.
We already run our own MCP server. Is this still useful?
Often, yes. Your server can stay: AnythingMCP can front an existing MCP server as a connector and add the audit log, roles and per-user sign-in that enterprise customers ask for, next to their other systems.
Our API is private or partner-only. Can we still take part?
Yes, as long as we get documentation and a test account. Customers then use the connector with their own credentials, as with any other API.