Use Discriminantly with another AI assistant
A remote MCP server with sign-in. Whether a given client works is something to test.
Remote MCP server
The facts.
- Address
https://www.discriminantly.com/mcp- Connection
- Remote MCP server
- Authentication
- Sign in to Discriminantly (OAuth) where the client supports it
- Availability
- Varies by client; verify before relying on it
- Directory
- None
Setup
3 steps.
- 1In your AI’s settings, add a remote MCP server (often called a connector or integration) at https://www.discriminantly.com/mcp.
- 2When asked, sign in to Discriminantly.
- 3Turn it on in a chat, then ask.
What you can ask
Start from a request, use your record, save what matters.
An empty account can begin with recommendations and planning; it simply has no records of yours to contribute yet. As you save things, requests can draw on them.
- Start from a request
Using Discriminantly, plan two days in Naples around classic cafés, pizza and tailoring.
- Use what you’ve saved
Turn my saved London places in Discriminantly into a weekend plan and recommend a few additions.
- Save something
Keep Hatchards in London in Discriminantly for me.
Suggested places stay recommendations until you keep them. A plan is not a record of going. Whether a given client uses Discriminantly for a request, and how, varies by client and model. Test with your own.
Once connected
The same record, from either side.
- Changes are recorded under the connection the client authorized. If the client declares its name when it connects (the MCP initialize handshake), that name is recorded; if it declares none, the record says the change came through your AI, without naming which.
- You can disconnect at any time in Settings › Connect to your AI. Access ends immediately; nothing is deleted.
- Private records stay private: only you and the assistants you have connected can see them. The one disclosed exception is a private travel mark used as a stop in a plan you share, whose name and address may appear to collaborators after you confirm.