Request a connector, or tell us one worked
Two forms, about a minute each, and neither needs a GitHub account. Use the request form to ask for a connector for a system you run. Use the receipt form after you ran a connector against your own live tenant and it did the job. A person reads every submission before anything is published, and plain email works just as well.
Request a connector
Your PSA, RMM, backup, security, or M365 tool is not covered yet? Tell us which one, and what you would ask it. Requests with more MSPs behind them move up the queue, and some get co-built live in a Build Session.
It asks for the vendor name, the category, one question you would ask that system in plain English, a link to its API docs if you happen to have one, roughly how big your MSP is, and whether you would like to watch it built live. Only your email and the vendor name are required; skip anything you do not know.
Tell us a connector worked
You ran a connector against your own tenant and it did the job. That is a receipt, and it is the most useful thing you can send us: a receipt from a real MSP is what flips a connector to Live-verified on the receipts wall.
It asks which connector you ran, what you ran or asked in your own words, what kind of tenant it was, and whether we may credit your MSP publicly. Only your email and the connector name are required.
What happens after you send one
- A person reads it first. Nothing is auto-published.
- After that review it becomes a public GitHub issue on the MSP Skills project, so other MSPs can read it, vote on it, and see the same thing you saw. We file that issue for you.
- We email you if we have a question. Your email address is not part of the public issue, and on the receipt form your MSP is named only if you ticked the credit box.
Prefer plain email
Email hello@servosity.com instead. For a request, name the system and one question you would ask it. For a receipt, name the connector and what you ran. Plain text is perfect: no markdown, no issue tracker, no account.
Already have a GitHub account
Then file it yourself and skip the handoff. How to request a Skill walks through the GitHub route step by step, and the contributor guide covers bug reports, small fixes, and whole connectors.