Dify

Hosted LLM app builder — GUI-only, remote MCP with custom headers.

cloud API key
verified

Dify is a hosted (or self-hosted) LLM app-building platform — it only connects to remote MCP servers over HTTP, added through its own UI rather than a config file. There's no local/stdio mode since Dify doesn't spawn subprocesses on your machine. Verified against a real Dify installation.

Cloud (API key)

In Dify: Tools → MCP → add a server, and fill in:

Server URL: https://api.yliuai.com/mcp-apikey/
Name: anything, e.g. Spomory
Server Identifier: a unique short ID (max 24 characters)
Advanced Options → Custom Headers: x-api-key → <your key>

Verified against a real Dify installation, resolving to the same account/memory graph as every other client on this page.

Where does <your key> come from?

Get one instantly with curl — fine for your own testing:

curl -X POST https://api.yliuai.com/users/register \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com"}'
# the api_key in the response (starts with mck_) is shown only this once -- save it

That hands you a key with no proof you control the email — fine for testing, but for real use, get one through the email-confirmation form instead, which actually verifies the address.

Get a verified key on the Cloud & Apps page →

Dify's MCP docs →

Make it actually get used

Connecting the tools doesn't mean your client reaches for them on its own — it needs to be told to call search_memory before answering and add_memory after you share something worth keeping. SKILL.md is a short instructions file that does that. How you load it is specific to each client: some auto-discover a skills folder the same way Claude Code does, others only have a custom-instructions or system-prompt field instead. Verified for this one:

Dify doesn't auto-discover a skills file — paste SKILL.md's content into the Agent app's "Instructions" field in Studio instead.

SKILL.md on GitHub →