🐣 Good first issue: contribute a new MCP adapter

[keysersoft]

👋 New here? Adding a pre-built MCP adapter is the most beginner-friendly way to contribute — it's typically a single JSON file and takes ~30 minutes once you've picked a target.

Pick a target

Browse the community wishlist and grab whichever SaaS has the most 👍. Comment on this issue saying which one you'll work on so we don't duplicate effort.

Step-by-step

1. Fork the repo and create a branch (adapter/<saas-slug>).
2. Pick an existing adapter close to yours as template:
   • For a REST API: see packages/backend/src/adapters/de/dhl.json or vies-vat.json
   • For a GraphQL service: see shopware-6.json
   • For a SOAP/WSDL service: see handelsregister.json
3. Copy it, rename it your-saas.json, and update:
   • name, description, baseUrl
   • auth block (OAuth2, API Key, Basic, etc.)
   • tools[] — one entry per API endpoint you want to expose
4. Register it in packages/backend/src/catalog.ts.
5. The parametrised catalog.spec.ts test will validate it on npm test. If your adapter has unusual params, add a focused test in packages/backend/src/adapters/__tests__/.
6. Open a PR. Tag @keysersoft for review.

What we look for in a good adapter

• ✅ Real, useful tools (not just "list everything")
• ✅ Clear description strings — the AI uses them to decide when to call the tool
• ✅ Path/query/body parameters mapped explicitly (don't rely on auto-detection alone)
• ✅ Auth correctly scoped (least privilege wins)
• ✅ At least one example value per tool

Resources

• 📖 Tool Definition Format — the JSON schema
• 📖 Connector Guides
• 📖 Existing adapters — copy-paste-friendly templates
• 💬 Stuck? Ping us in Discussions / Q&A

We're happy to pair on the first PR — don't be shy 🙌