Connecting Other MCP Tools
Fuze Store works with any tool that supports the Model Context Protocol and OAuth2 with PKCE. Most need only your link, find the sign-in endpoints themselves and register themselves.
Before you start
- The AI Connections add-on on the store.
- Owner, organization admin, or a role with AI Connections → Connect.
Steps
Copy your store's link
In the Fuze Store app open Configurations → MCP → Connect an assistant and copy the MCP Server URL. It looks like https://api.fuze-store.com/mcp/store/<your-store-id>. It is unique to one store, so there is no store picker on the approval screen.
Add a remote MCP server
In your tool add a remote or custom MCP server and paste your link. The menu varies, often Settings, Connectors, MCP or a config file.
Add a remote MCP server — screenshot coming soon
Let it register and sign in
The tool discovers the endpoints, registers itself (RFC 7591 dynamic client registration) and opens your browser.
Let it register and sign in — screenshot coming soon
Approve
Sign in to Fuze Store if asked, review the permissions and Approve.
Approve — screenshot coming soon
What happens next
- The assistant appears under Active connections on Configurations → MCP, with its name, who connected it, the permissions granted and when its key expires. Start asking questions about your store.
Edge cases
- Tools that cannot open a browser need a client ID and secret made on Configurations → MCP → Credentials. See Setting Up AI Access.
- Known to work, all free: Zed, Kiro (AWS), Amazon Q Developer CLI, OpenCode and Docker MCP Toolkit.
- Needs a bridge. Cline and Continue.dev accept remote URLs but hand the sign-in to the
mcp-remotepackage, so expect one extra step and check their current docs. - If it cannot discover the server, confirm it supports remote MCP over HTTP and OAuth2 PKCE.
- Sign-in problems. The usual causes are not being signed in to Fuze Store in the browser, the AI Connections add-on being off, or pasting the link for a different store. See Setting Up AI Access.
- Your role limits what you can grant. You can only give permissions your own role holds. A role without AI Connections → Connect is refused at sign-in.
- No client ID is needed for tools that register themselves from the link alone.
Works with
| Add-on or plan | What changes on this page |
|---|---|
| AI Connections add-on | Required on the store. Paid, and free during the free trial and early release. The AI vendor may also need a paid plan, which is separate. |
| Vendor plan | Varies. See Which AI Tools Work Where. |