Test your MCP server with Meta Muse.
Meta's Muse Connector Platform accepts API and MCP connectors. Knotbind can test your server contract and record a real Muse connection through the relay; it does not submit or claim directory approval for you.
What we verified
Meta's official Muse Connector guidelines describe a connector submission and review process, API/MCP support, tool permission classification, business verification, privacy and data-processing review, credentials and test-user information. This is separate from adding a custom connector in the Muse app.
Try a custom connector
-
Open the Muse app's Connectors settings
Choose to create a Custom Connector and use the Streamable HTTP MCP URL from your Knotbind MCP Tools page.
-
Choose authentication
Use OAuth if the MCP server requires a user sign-in. Select no sign-in only for a deliberately public endpoint. A public endpoint lets anyone who has its URL call its public tools.
-
Test a read-only tool
Ask Muse to list the tools, then call a harmless read-only tool and compare the answer with the source service.
-
Record the actual result
In Knotbind → Assistants → Meta Muse, choose Yes or No and write what you observed. A Knotbind contract Check alone does not count as a real Muse test.
Before directory submission
| Prepare | What reviewers need |
|---|---|
| Business | Verified organization details and proof of authority to publish. |
| Privacy and data | Privacy policy, data-processing answers, retention, deletion and security practices. |
| Connector | Public HTTPS endpoint, authentication method, scopes, tested tools and accurate read/write/sensitive-write classifications. |
| Review access | Dedicated test account, sample data and a walkthrough for each tool. |
| Operational quality | Complete task flows, confirmed versus pending results, safe retries, support contacts and incident response. |