Use casesWorks with
Connect Make scenarios and AI agents to a shared memory
Make connects to Context Engine through its built-in MCP Client app: add a new MCP server with the Context Engine address and sign in, and the memory tools load into your scenario or AI agent; an HTTP module can also save memories with a key.
What it does
A Make scenario that drafts replies, qualifies leads or prepares a meeting is only as good as what it knows about the customer. With Context Engine, it can read what the team and other AI tools saved, and save the result back so everyone starts from it next time.
Connect it (MCP Client)
- In Context Engine, open AI tools, then Connect an AI tool, and choose Another MCP app. Pick its engines and copy the address.
- In Make, add the MCP Client module and click Create a connection.
- In the MCP Server field, click + New MCP Server, paste the address and choose OAuth. Sign in and allow the engines.
- Make loads the tools. Use them in the module, or give them to an AI agent.
Save with an HTTP module
For a scenario with no AI step, an HTTP module can POST to https://app.contextengine.com/tool/write with Authorization: Bearer <key> and a JSON body naming the engine, the type and a title. Make the key in Connect an AI tool → Your own code, one per scenario.
Questions
Does Context Engine need a Make custom app?
No. Make's MCP Client app connects to remote MCP servers that are not on its list through + New MCP Server, with OAuth.
What can a Make scenario do with the memory?
Search it by meaning, open a memory, and write or edit notes, decisions, tasks, people, customers and meetings, in the engines the connection reaches.